Configuration migration assistant

What you configure

input options

Supply the supported legacy configuration to the migration assistant.

options / requiredModules

Inspect the draft WTS options and the optional modules it identifies.

issues / unmappedOptions

Review diagnostics and manually resolve unsupported or ambiguous settings.

Integration code example

1. Inventory existing views, callbacks, resource settings, and date behavior.
2. Run the licensed migration assistant and treat its output as a reviewable draft.
3. Complete application tests for time zones, recurrence, interactions, accessibility, and visual behavior.

Copy this TypeScript into your application, not the browser console. Replace YOUR_WTS_LICENSE_KEY with an entitlement issued for your deployment origin. A WTS license is not a Google, Microsoft or CalDAV credential. These examples are documentation only and never execute on this page.

npm install @wts-calendar/core

import { verifyCalendarLicense } from '@wts-calendar/core';
import { PremiumCalendarInteroperability } from '@wts-calendar/core/premium-interoperability';

const license = await verifyCalendarLicense('YOUR_WTS_LICENSE_KEY');
const interoperability = new PremiumCalendarInteroperability({ license });

// Use the exact exported migration method; the output is a draft, not drop-in parity.
export function inspectMigration(legacyOptions: Readonly<Record<string, unknown>>) {
  const draft = interoperability.migrateFullCalendarOptions(legacyOptions);
  return {
    options: draft.options,
    modulesToInstall: draft.requiredModules,
    review: draft.issues,
    unmapped: draft.unmappedOptions,
  };
}
export const example = inspectMigration({
  initialView: 'resourceTimelineWeek',
  initialDate: '2026-09-07',
  firstDay: 1,
  slotDuration: '00:30:00',
  editable: true,
});

Application responsibilities

Review diagnostics and unmapped options, register the reported modules, and test callback payloads before using the draft. A WTS entitlement must be obtained separately.

Behavior and lifecycle

• Supported aliases and layout settings are translated while unmapped options remain visible.
• Callback payloads are flagged for review, and third-party license keys are not converted into WTS grants.