@innosolutions/inno-calendar 1.0.63 → 1.0.65

package/README.md

@@ -221,9 +221,9 @@ function CalendarContent() {
 }
 ```
 
-## Resource Views
+## Resource & Timeline Views
 
-The resource views (`resource-day`, `resource-week`) group events by resource and render one row per resource.
+The resource-based views (`resource-day`, `resource-week`, `timeline-day`, `timeline-3day`, `timeline-week`) group events by resource and render one row per resource.
 
 **Default flow** — resource rows are derived from the events: each unique resource referenced by an event (via `event.resourceId`, `event.data.user`, `event.user`, or `event.participants`) gets its own row. Resources without events are not shown.
 
@@ -232,7 +232,7 @@ The resource views (`resource-day`, `resource-week`) group events by resource an
 ```tsx
 <InnoCalendar
   events={events}
-  initialView="resource-week"
+  initialView="timeline-week"
   alwaysShowResources={[
     { id: "room-1", name: "Meeting Room A", avatar: "/rooms/a.jpg" },
     { id: "room-2", name: "Meeting Room B" },
@@ -240,9 +240,9 @@ The resource views (`resource-day`, `resource-week`) group events by resource an
 />
 ```
 
-Each entry accepts the full `ICalendarUser` shape — at minimum `id` and `name` are needed to render the row header; `avatar` and `email` are optional. Updating the array re-renders the resource view immediately.
+Each entry accepts the full `ICalendarUser` shape — at minimum `id` and `name` are needed to render the row header; `avatar` and `email` are optional. Updating the array re-renders the view immediately.
 
-This prop is scoped to the resource views only — it is ignored in `timeline-*` and all other views.
+This prop applies to all resource-based views (`resource-day`, `resource-week`, `timeline-day`, `timeline-3day`, `timeline-week`) and is ignored in `day`, `week`, `month`, `year`, and `agenda` views.
 
 ## Working Hours