Repeated-task views
Present categorized task occurrences across a month or week. This is a dedicated task-oriented layout, distinct from ordinary recurring events in the standard calendar.
Loading interactive demo…
What you configure
- view
- Choose monthly-repeated-task or weekly-repeated-task.
- task / taskSources
- Supply task categories and their occurrences statically or through sources.
- IDs and versions
- Keep category and occurrence IDs stable; preserve optional concurrency versions.
Essential integration
This assumes the shared Quick start already provides premiumLicense and, for UI views, premiumCalendarOptions. Only the feature-specific setup is shown.
import { WtsCalendar } from '@wts-calendar/core';
import { repeatedTasksModule } from '@wts-calendar/core/repeated-tasks';
const calendar = new WtsCalendar({
...premiumCalendarOptions,
plugins: [repeatedTasksModule],
view: 'weekly-repeated-task',
headerToolbar: {
start: 'prev,next',
center: 'title',
end: 'weekly-repeated-task,monthly-repeated-task',
},
task: [
{
id: 'checks',
name: 'checks',
title: 'Equipment checks',
enable: true,
color: '#18796b',
icon: '',
data: [
{
id: 'inspection',
start: '2026-09-07',
end: '2026-09-07',
reason: 'Safety inspection',
status: 'pending',
},
],
},
],
});
export function completeInspection() {
calendar.setTaskStatus('checks', 'inspection', 'completed');
}Behavior and lifecycle
- Source refreshes replace their owned task snapshot without removing static or other-source tasks.
- Stable occurrence IDs allow paginated data to merge and later refreshes to reconcile records.
Limits and responsibilities
- These Premium views are not required for standard recurring calendar events.
- No task database or background task-execution service is included.
Premium
Enable this capability
- Optional module
- @wts-calendar/core/repeated-tasks
- Local capability ID
- repeated-task-views · 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.