Premium

Configuration migration assistant

Translate supported legacy calendar configuration into a WTS draft and make remaining work visible. The assistant reports required modules, migration issues, and options that have no registered lossless mapping.

Loading interactive demo…

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.

Essential integration

This assumes the shared Quick start already provides premiumLicense and, for UI views, premiumCalendarOptions. Only the feature-specific setup is shown.

Feature-specific TypeScript
import { PremiumCalendarInteroperability } from '@wts-calendar/core/premium-interoperability';

const interoperability = new PremiumCalendarInteroperability({ license: premiumLicense });

// 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,
});

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.

Limits and responsibilities

  • This is a configuration assistant, not a source-compatible drop-in replacement for every API or DOM hook.
  • Do not remove the old integration until application-level acceptance checks pass.
Premium

Enable this capability

Optional module
@wts-calendar/core/premium-interoperability
Local capability ID
premium-interoperability · enabled by package-wide Premium

Use the request form to describe your project and deployment origins. Pricing and terms are confirmed privately. A WTS license is separate from provider credentials; do not send passwords or production access tokens.

The live example uses a browser-visible deployment key restricted to this package and approved origins. It does not collect license keys or visitor credentials.

Request Premium pricing

Share the details we need to respond to your request.

Optional for this inquiry, but required before deployment. Add one origin per line without a page path. Registered HTTP localhost origins are allowed for development.

Don’t include license keys, passwords, or confidential information.