@bryntum/calendar-vue-3 7.2.0 → 7.2.2

package/src/components/BryntumTimelineHistogram.vue

@@ -914,7 +914,7 @@ defineProps<{
     rootElement ? : ShadowRoot|HTMLElement
     /**
      * Row height in pixels. This allows the default height for rows to be controlled. Note that it may be
-     * overriden by specifying a [rowHeight](https://bryntum.com/products/calendar/docs/api/Grid/data/GridRowModel#field-rowHeight) on a per record basis, or from
+     * overridden by specifying a [rowHeight](https://bryntum.com/products/calendar/docs/api/Grid/data/GridRowModel#field-rowHeight) on a per record basis, or from
      * a column [renderer](https://bryntum.com/products/calendar/docs/api/Grid/column/Column#config-renderer).
      * ...
      * [View online docs...](https://bryntum.com/products/calendar/docs/api/Scheduler/view/TimelineHistogram#config-rowHeight)
@@ -1288,7 +1288,7 @@ defineProps<{
     cellEditFeature ? : object|Boolean|string|CellEdit|CellEditConfig
     /**
      * Right click to display context menu for cells. To invoke the cell menu in a keyboard-accessible manner, use the
-     * `SPACE` key when the cell is focused.
+     * <kbd>Space</kbd> key when the cell is focused.
      * ...
      * [View online docs...](https://bryntum.com/products/calendar/docs/api/Grid/feature/CellMenu)
      */
@@ -1396,8 +1396,8 @@ defineProps<{
     filterBarFeature ? : object|Boolean|string|FilterBar|FilterBarConfig
     /**
      * Enables rendering and handling of row groups. The actual grouping is done in the store, but triggered by
-     * <kbd>shift</kbd> + clicking headers, or by using the context menu, or by using two finger tap (one on header,
-     * one anywhere on grid). Use <kbd>shift</kbd> + <kbd>alt</kbd> + click, or the context menu, to remove a column
+     * <kbd>Shift</kbd> + clicking headers, or by using the context menu, or by using two finger tap (one on header,
+     * one anywhere on grid). Use <kbd>Shift</kbd> + <kbd>Alt</kbd> + click, or the context menu, to remove a column
      * grouper.
      * ...
      * [View online docs...](https://bryntum.com/products/calendar/docs/api/Grid/feature/Group)
@@ -1611,7 +1611,7 @@ defineProps<{
 
 const emit = defineEmits<{
     /**
-     * Fires before an assignment is removed. Can be triggered by user pressing [DELETE] or [BACKSPACE] or
+     * Fires before an assignment is removed. Can be triggered by user pressing <kbd>Delete</kbd> or <kbd>Backspace</kbd> or
      * by the event editor. Can for example be used to display a custom dialog to confirm deletion, in which
      * case records should be "manually" removed after confirmation:
      * ...
@@ -1656,7 +1656,7 @@ const emit = defineEmits<{
      */
     (e: 'beforeCellEditStart', params: ((event: { source: Grid, editorContext: CellEditorContext }) => Promise<boolean>|boolean|void)|string): Promise<boolean>|boolean|void
     /**
-     * Fires on the owning Grid before deleting a range of selected cell values by pressing `Backspace` or `Del`
+     * Fires on the owning Grid before deleting a range of selected cell values by pressing <kbd>Backspace</kbd> or <kbd>Delete</kbd>
      * buttons while [autoEdit](https://bryntum.com/products/calendar/docs/api/Grid/feature/CellEdit#config-autoEdit) is set to `true`. Return `false` to prevent editing.
      * @param {string} e Event name
      * @param {object} params Event parameters
@@ -1752,7 +1752,7 @@ const emit = defineEmits<{
      */
     (e: 'beforeDestroy', params: ((event: { source: Base }) => void)|string): void
     /**
-     * Fires before an event is removed. Can be triggered by user pressing [DELETE] or [BACKSPACE] or by the
+     * Fires before an event is removed. Can be triggered by user pressing <kbd>Delete</kbd> or <kbd>Backspace</kbd> or by the
      * event editor. Return `false` to immediately veto the removal (or a `Promise` yielding `true` or `false`
      * for async vetoing).
      * ...
@@ -2714,7 +2714,7 @@ const emit = defineEmits<{
      * @param {Response} params.event.response Optional response, if received
      * @param {Error} params.event.error Optional error, if exception occurred
      */
-    (e: 'pdfExport', params: ((event: { response?: any, error?: Error }) => void)|string): void
+    (e: 'pdfExport', params: ((event: { response?: Response, error?: Error }) => void)|string): void
     /**
      * Fired after the [viewPreset](https://bryntum.com/products/calendar/docs/api/Scheduler/view/mixin/TimelineViewPresets#config-viewPreset) has changed.
      * @param {string} e Event name
@@ -3272,6 +3272,16 @@ const emit = defineEmits<{
      * @param {Core.widget.Tool} params.event.tool The tool which is being clicked.
      */
     (e: 'toolClick', params: ((event: { source: Tool, tool: Tool }) => void)|string): void
+    /**
+     * Fired on the owning Grid/Scheduler/Gantt after tree grouping levels change
+     * @param {string} e Event name
+     * @param {object} params Event parameters
+     * @param {object} params.event Event object
+     * @param {Grid.view.Grid} params.event.source The grid instance
+     * @param {(string|Function)[]} params.event.groupers Array of field names or functions representing the current grouping levels
+     * @param {(string|Function)[]} params.event.oldGroupers Array of field names or functions representing the previous grouping levels
+     */
+    (e: 'treeGroup', params: ((event: { source: Grid, groupers: (string|Function)[], oldGroupers: (string|Function)[] }) => void)|string): void
     /**
      * Fires when row locking is disabled.
      * @param {string} e Event name
@@ -3677,6 +3687,7 @@ const widgetData = {
         'onToggleGroup',
         'onToggleNode',
         'onToolClick',
+        'onTreeGroup',
         'onUnlockRows',
         'onUnsplit',
         'onVisibleDateRangeChange',
@@ -3880,6 +3891,7 @@ const widgetData = {
         'toggleGroup',
         'toggleNode',
         'toolClick',
+        'treeGroup',
         'unlockRows',
         'unsplit',
         'visibleDateRangeChange'

package/src/components/BryntumTimelineHistogramProps.ts

@@ -877,7 +877,7 @@ export declare type BryntumTimelineHistogramProps = {
     rootElement ? : ShadowRoot|HTMLElement
     /**
      * Row height in pixels. This allows the default height for rows to be controlled. Note that it may be
-     * overriden by specifying a [rowHeight](https://bryntum.com/products/calendar/docs/api/Grid/data/GridRowModel#field-rowHeight) on a per record basis, or from
+     * overridden by specifying a [rowHeight](https://bryntum.com/products/calendar/docs/api/Grid/data/GridRowModel#field-rowHeight) on a per record basis, or from
      * a column [renderer](https://bryntum.com/products/calendar/docs/api/Grid/column/Column#config-renderer).
      * ...
      * [View online docs...](https://bryntum.com/products/calendar/docs/api/Scheduler/view/TimelineHistogram#config-rowHeight)
@@ -1251,7 +1251,7 @@ export declare type BryntumTimelineHistogramProps = {
     cellEditFeature ? : object|Boolean|string|CellEdit|CellEditConfig
     /**
      * Right click to display context menu for cells. To invoke the cell menu in a keyboard-accessible manner, use the
-     * `SPACE` key when the cell is focused.
+     * <kbd>Space</kbd> key when the cell is focused.
      * ...
      * [View online docs...](https://bryntum.com/products/calendar/docs/api/Grid/feature/CellMenu)
      */
@@ -1359,8 +1359,8 @@ export declare type BryntumTimelineHistogramProps = {
     filterBarFeature ? : object|Boolean|string|FilterBar|FilterBarConfig
     /**
      * Enables rendering and handling of row groups. The actual grouping is done in the store, but triggered by
-     * <kbd>shift</kbd> + clicking headers, or by using the context menu, or by using two finger tap (one on header,
-     * one anywhere on grid). Use <kbd>shift</kbd> + <kbd>alt</kbd> + click, or the context menu, to remove a column
+     * <kbd>Shift</kbd> + clicking headers, or by using the context menu, or by using two finger tap (one on header,
+     * one anywhere on grid). Use <kbd>Shift</kbd> + <kbd>Alt</kbd> + click, or the context menu, to remove a column
      * grouper.
      * ...
      * [View online docs...](https://bryntum.com/products/calendar/docs/api/Grid/feature/Group)

package/src/components/BryntumTreeCombo.vue

@@ -189,7 +189,7 @@ defineProps<{
     contentElementCls ? : string|object
     /**
      * If configured as `true`, this means that when an unmatched string is typed into the
-     * combo's input field, and `ENTER`, or the [multiValueSeparator](https://bryntum.com/products/calendar/docs/api/Core/widget/Combo#config-multiValueSeparator) is typed,
+     * combo's input field, and <kbd>Enter</kbd>, or the [multiValueSeparator](https://bryntum.com/products/calendar/docs/api/Core/widget/Combo#config-multiValueSeparator) is typed,
      * a new record will be created using the typed string as the [displayField](https://bryntum.com/products/calendar/docs/api/Core/widget/Combo#config-displayField).
      * ...
      * [View online docs...](https://bryntum.com/products/calendar/docs/api/Grid/widget/TreeCombo#config-createOnUnmatched)
@@ -684,7 +684,7 @@ defineProps<{
     required ? : Boolean
     /**
      * If this field is not [readOnly](https://bryntum.com/products/calendar/docs/api/Core/widget/Field#config-readOnly), then setting this option means that pressing
-     * the `ESCAPE` key after editing the field will revert the field to the value it had when
+     * the <kbd>Escape</kbd> key after editing the field will revert the field to the value it had when
      * the user focused the field. If the field is *not* changed from when focused, the [clearable](https://bryntum.com/products/calendar/docs/api/Core/widget/Field#config-clearable)
      * behaviour will be activated.
      */

package/src/components/BryntumTreeComboProps.ts

@@ -175,7 +175,7 @@ export declare type BryntumTreeComboProps = {
     contentElementCls ? : string|object
     /**
      * If configured as `true`, this means that when an unmatched string is typed into the
-     * combo's input field, and `ENTER`, or the [multiValueSeparator](https://bryntum.com/products/calendar/docs/api/Core/widget/Combo#config-multiValueSeparator) is typed,
+     * combo's input field, and <kbd>Enter</kbd>, or the [multiValueSeparator](https://bryntum.com/products/calendar/docs/api/Core/widget/Combo#config-multiValueSeparator) is typed,
      * a new record will be created using the typed string as the [displayField](https://bryntum.com/products/calendar/docs/api/Core/widget/Combo#config-displayField).
      * ...
      * [View online docs...](https://bryntum.com/products/calendar/docs/api/Grid/widget/TreeCombo#config-createOnUnmatched)
@@ -670,7 +670,7 @@ export declare type BryntumTreeComboProps = {
     required ? : Boolean
     /**
      * If this field is not [readOnly](https://bryntum.com/products/calendar/docs/api/Core/widget/Field#config-readOnly), then setting this option means that pressing
-     * the `ESCAPE` key after editing the field will revert the field to the value it had when
+     * the <kbd>Escape</kbd> key after editing the field will revert the field to the value it had when
      * the user focused the field. If the field is *not* changed from when focused, the [clearable](https://bryntum.com/products/calendar/docs/api/Core/widget/Field#config-clearable)
      * behaviour will be activated.
      */

package/src/components/BryntumTreeGrid.vue

@@ -590,7 +590,7 @@ defineProps<{
     rootElement ? : ShadowRoot|HTMLElement
     /**
      * Row height in pixels. This allows the default height for rows to be controlled. Note that it may be
-     * overriden by specifying a [rowHeight](https://bryntum.com/products/calendar/docs/api/Grid/data/GridRowModel#field-rowHeight) on a per record basis, or from
+     * overridden by specifying a [rowHeight](https://bryntum.com/products/calendar/docs/api/Grid/data/GridRowModel#field-rowHeight) on a per record basis, or from
      * a column [renderer](https://bryntum.com/products/calendar/docs/api/Grid/column/Column#config-renderer).
      * ...
      * [View online docs...](https://bryntum.com/products/calendar/docs/api/Grid/view/TreeGrid#config-rowHeight)
@@ -818,7 +818,7 @@ defineProps<{
     cellEditFeature ? : object|Boolean|string|CellEdit|CellEditConfig
     /**
      * Right click to display context menu for cells. To invoke the cell menu in a keyboard-accessible manner, use the
-     * `SPACE` key when the cell is focused.
+     * <kbd>Space</kbd> key when the cell is focused.
      * ...
      * [View online docs...](https://bryntum.com/products/calendar/docs/api/Grid/feature/CellMenu)
      */
@@ -918,8 +918,8 @@ defineProps<{
     filterBarFeature ? : object|Boolean|string|FilterBar|FilterBarConfig
     /**
      * Enables rendering and handling of row groups. The actual grouping is done in the store, but triggered by
-     * <kbd>shift</kbd> + clicking headers, or by using the context menu, or by using two finger tap (one on header,
-     * one anywhere on grid). Use <kbd>shift</kbd> + <kbd>alt</kbd> + click, or the context menu, to remove a column
+     * <kbd>Shift</kbd> + clicking headers, or by using the context menu, or by using two finger tap (one on header,
+     * one anywhere on grid). Use <kbd>Shift</kbd> + <kbd>Alt</kbd> + click, or the context menu, to remove a column
      * grouper.
      * ...
      * [View online docs...](https://bryntum.com/products/calendar/docs/api/Grid/feature/Group)
@@ -1108,7 +1108,7 @@ const emit = defineEmits<{
      */
     (e: 'beforeCellEditStart', params: ((event: { source: Grid, editorContext: CellEditorContext }) => Promise<boolean>|boolean|void)|string): Promise<boolean>|boolean|void
     /**
-     * Fires on the owning Grid before deleting a range of selected cell values by pressing `Backspace` or `Del`
+     * Fires on the owning Grid before deleting a range of selected cell values by pressing <kbd>Backspace</kbd> or <kbd>Delete</kbd>
      * buttons while [autoEdit](https://bryntum.com/products/calendar/docs/api/Grid/feature/CellEdit#config-autoEdit) is set to `true`. Return `false` to prevent editing.
      * @param {string} e Event name
      * @param {object} params Event parameters
@@ -2044,7 +2044,7 @@ const emit = defineEmits<{
      * @param {Response} params.event.response Optional response, if received
      * @param {Error} params.event.error Optional error, if exception occurred
      */
-    (e: 'pdfExport', params: ((event: { response?: any, error?: Error }) => void)|string): void
+    (e: 'pdfExport', params: ((event: { response?: Response, error?: Error }) => void)|string): void
     /**
      * Fired when a Widget's read only state is toggled
      * @param {string} e Event name
@@ -2305,6 +2305,16 @@ const emit = defineEmits<{
      * @param {Core.widget.Tool} params.event.tool The tool which is being clicked.
      */
     (e: 'toolClick', params: ((event: { source: Tool, tool: Tool }) => void)|string): void
+    /**
+     * Fired on the owning Grid/Scheduler/Gantt after tree grouping levels change
+     * @param {string} e Event name
+     * @param {object} params Event parameters
+     * @param {object} params.event Event object
+     * @param {Grid.view.Grid} params.event.source The grid instance
+     * @param {(string|Function)[]} params.event.groupers Array of field names or functions representing the current grouping levels
+     * @param {(string|Function)[]} params.event.oldGroupers Array of field names or functions representing the previous grouping levels
+     */
+    (e: 'treeGroup', params: ((event: { source: Grid, groupers: (string|Function)[], oldGroupers: (string|Function)[] }) => void)|string): void
     /**
      * Fires when row locking is disabled.
      * @param {string} e Event name
@@ -2597,6 +2607,7 @@ const widgetData = {
         'onToggleGroup',
         'onToggleNode',
         'onToolClick',
+        'onTreeGroup',
         'onUnlockRows',
         'onUnsplit',
         'preserveScroll',
@@ -2746,6 +2757,7 @@ const widgetData = {
         'toggleGroup',
         'toggleNode',
         'toolClick',
+        'treeGroup',
         'unlockRows',
         'unsplit'
     ]

package/src/components/BryntumTreeGridProps.ts

@@ -553,7 +553,7 @@ export declare type BryntumTreeGridProps = {
     rootElement ? : ShadowRoot|HTMLElement
     /**
      * Row height in pixels. This allows the default height for rows to be controlled. Note that it may be
-     * overriden by specifying a [rowHeight](https://bryntum.com/products/calendar/docs/api/Grid/data/GridRowModel#field-rowHeight) on a per record basis, or from
+     * overridden by specifying a [rowHeight](https://bryntum.com/products/calendar/docs/api/Grid/data/GridRowModel#field-rowHeight) on a per record basis, or from
      * a column [renderer](https://bryntum.com/products/calendar/docs/api/Grid/column/Column#config-renderer).
      * ...
      * [View online docs...](https://bryntum.com/products/calendar/docs/api/Grid/view/TreeGrid#config-rowHeight)
@@ -781,7 +781,7 @@ export declare type BryntumTreeGridProps = {
     cellEditFeature ? : object|Boolean|string|CellEdit|CellEditConfig
     /**
      * Right click to display context menu for cells. To invoke the cell menu in a keyboard-accessible manner, use the
-     * `SPACE` key when the cell is focused.
+     * <kbd>Space</kbd> key when the cell is focused.
      * ...
      * [View online docs...](https://bryntum.com/products/calendar/docs/api/Grid/feature/CellMenu)
      */
@@ -881,8 +881,8 @@ export declare type BryntumTreeGridProps = {
     filterBarFeature ? : object|Boolean|string|FilterBar|FilterBarConfig
     /**
      * Enables rendering and handling of row groups. The actual grouping is done in the store, but triggered by
-     * <kbd>shift</kbd> + clicking headers, or by using the context menu, or by using two finger tap (one on header,
-     * one anywhere on grid). Use <kbd>shift</kbd> + <kbd>alt</kbd> + click, or the context menu, to remove a column
+     * <kbd>Shift</kbd> + clicking headers, or by using the context menu, or by using two finger tap (one on header,
+     * one anywhere on grid). Use <kbd>Shift</kbd> + <kbd>Alt</kbd> + click, or the context menu, to remove a column
      * grouper.
      * ...
      * [View online docs...](https://bryntum.com/products/calendar/docs/api/Grid/feature/Group)

package/src/components/BryntumWeekView.vue

@@ -502,7 +502,7 @@ defineProps<{
      * @param {object} detail.renderData.dataset An object which produces the `dataset` of the resulting event bar
      * @param {boolean} detail.renderData.solidBar This is valid for views which create event bars. This is set to `true` by default for all day and interday events so that these appear as a solid block of background color. An eventRenderer may mutate this flag to change in what manner the event bar is colored - as a solid bar of color, or using the foreground color (text and icons) such as the MonthView, the CalendarRow (all day events in a DayView), and OverflowPopups
      * @param {string} detail.renderData.bodyColor When used in a [DayView](https://bryntum.com/products/calendar/docs/api/Calendar/widget/DayView), this color is applied to the body of the event element. Note that this must be light enough that the text color (From the SASS variable `$dayview-event-color`) is visible
-     * @param {boolean} detail.renderData.showBullet If there is no `iconCls`, and the event is not recurring, then by default a "bullet" circular icon is shown if the view's [showBullet](https://bryntum.com/products/calendar/docs/api/Calendar/widget/mixin/CalendarMixin#config-showBullet) if set. Setting this property in an event renderer overrides this behaviour.
+     * @param {boolean} detail.renderData.showBullet If there is no `iconCls`, and the event is not recurring, then by default a "bullet" circular icon is shown if the view's [showBullet](https://bryntum.com/products/calendar/docs/api/Calendar/widget/mixin/CalendarMixin#config-showBullet) if set. Setting this property in an event renderer overrides this behaviour. <h3>Using JSX (React)</h3> When using the Bryntum React wrapper, the event renderer can return JSX elements: ```javascript eventRenderer({ eventRecord, renderData }) {     return &lt;MyEventComponent event={eventRecord} />; } ``` *Using JSX in the event renderer creates a React portal for each rendered event. For calendars with many visible events or frequently re-rendered views, this may impact scrolling performance compared to returning plain strings or [DomConfig](https://bryntum.com/products/calendar/docs/api/Core/helper/DomHelper#typedef-DomConfig) objects. Consider using JSX primarily for events that require complex interactive React components.*
      * @returns {DomConfig,DomConfig[],string,void} The content to be used as the event body.
      */
     eventRenderer ? : ((detail: { view: CalendarView, eventRecord: EventModel, resourceRecord: ResourceModel, renderData: { style: object, cls: object, iconStyle: object, iconCls: object, eventColor: string, eventBackground: string, textColor: string, eventInnerStyle: object, dataset: object, solidBar: Boolean, bodyColor: string, showBullet: Boolean } }) => DomConfig|DomConfig[]|string|void)|string

package/src/components/BryntumWeekViewProps.ts

@@ -488,7 +488,7 @@ export declare type BryntumWeekViewProps = {
      * @param {object} detail.renderData.dataset An object which produces the `dataset` of the resulting event bar
      * @param {boolean} detail.renderData.solidBar This is valid for views which create event bars. This is set to `true` by default for all day and interday events so that these appear as a solid block of background color. An eventRenderer may mutate this flag to change in what manner the event bar is colored - as a solid bar of color, or using the foreground color (text and icons) such as the MonthView, the CalendarRow (all day events in a DayView), and OverflowPopups
      * @param {string} detail.renderData.bodyColor When used in a [DayView](https://bryntum.com/products/calendar/docs/api/Calendar/widget/DayView), this color is applied to the body of the event element. Note that this must be light enough that the text color (From the SASS variable `$dayview-event-color`) is visible
-     * @param {boolean} detail.renderData.showBullet If there is no `iconCls`, and the event is not recurring, then by default a "bullet" circular icon is shown if the view's [showBullet](https://bryntum.com/products/calendar/docs/api/Calendar/widget/mixin/CalendarMixin#config-showBullet) if set. Setting this property in an event renderer overrides this behaviour.
+     * @param {boolean} detail.renderData.showBullet If there is no `iconCls`, and the event is not recurring, then by default a "bullet" circular icon is shown if the view's [showBullet](https://bryntum.com/products/calendar/docs/api/Calendar/widget/mixin/CalendarMixin#config-showBullet) if set. Setting this property in an event renderer overrides this behaviour. <h3>Using JSX (React)</h3> When using the Bryntum React wrapper, the event renderer can return JSX elements: ```javascript eventRenderer({ eventRecord, renderData }) {     return &lt;MyEventComponent event={eventRecord} />; } ``` *Using JSX in the event renderer creates a React portal for each rendered event. For calendars with many visible events or frequently re-rendered views, this may impact scrolling performance compared to returning plain strings or [DomConfig](https://bryntum.com/products/calendar/docs/api/Core/helper/DomHelper#typedef-DomConfig) objects. Consider using JSX primarily for events that require complex interactive React components.*
      * @returns {DomConfig,DomConfig[],string,void} The content to be used as the event body.
      */
     eventRenderer ? : ((detail: { view: CalendarView, eventRecord: EventModel, resourceRecord: ResourceModel, renderData: { style: object, cls: object, iconStyle: object, iconCls: object, eventColor: string, eventBackground: string, textColor: string, eventInnerStyle: object, dataset: object, solidBar: Boolean, bodyColor: string, showBullet: Boolean } }) => DomConfig|DomConfig[]|string|void)|string

package/src/components/BryntumYearView.vue

@@ -415,7 +415,7 @@ defineProps<{
      * @param {object} detail.renderData.dataset An object which produces the `dataset` of the resulting event bar
      * @param {boolean} detail.renderData.solidBar This is valid for views which create event bars. This is set to `true` by default for all day and interday events so that these appear as a solid block of background color. An eventRenderer may mutate this flag to change in what manner the event bar is colored - as a solid bar of color, or using the foreground color (text and icons) such as the MonthView, the CalendarRow (all day events in a DayView), and OverflowPopups
      * @param {string} detail.renderData.bodyColor When used in a [DayView](https://bryntum.com/products/calendar/docs/api/Calendar/widget/DayView), this color is applied to the body of the event element. Note that this must be light enough that the text color (From the SASS variable `$dayview-event-color`) is visible
-     * @param {boolean} detail.renderData.showBullet If there is no `iconCls`, and the event is not recurring, then by default a "bullet" circular icon is shown if the view's [showBullet](https://bryntum.com/products/calendar/docs/api/Calendar/widget/mixin/CalendarMixin#config-showBullet) if set. Setting this property in an event renderer overrides this behaviour.
+     * @param {boolean} detail.renderData.showBullet If there is no `iconCls`, and the event is not recurring, then by default a "bullet" circular icon is shown if the view's [showBullet](https://bryntum.com/products/calendar/docs/api/Calendar/widget/mixin/CalendarMixin#config-showBullet) if set. Setting this property in an event renderer overrides this behaviour. <h3>Using JSX (React)</h3> When using the Bryntum React wrapper, the event renderer can return JSX elements: ```javascript eventRenderer({ eventRecord, renderData }) {     return &lt;MyEventComponent event={eventRecord} />; } ``` *Using JSX in the event renderer creates a React portal for each rendered event. For calendars with many visible events or frequently re-rendered views, this may impact scrolling performance compared to returning plain strings or [DomConfig](https://bryntum.com/products/calendar/docs/api/Core/helper/DomHelper#typedef-DomConfig) objects. Consider using JSX primarily for events that require complex interactive React components.*
      * @returns {DomConfig,DomConfig[],string,void} The content to be used as the event body.
      */
     eventRenderer ? : ((detail: { view: CalendarView, eventRecord: EventModel, resourceRecord: ResourceModel, renderData: { style: object, cls: object, iconStyle: object, iconCls: object, eventColor: string, eventBackground: string, textColor: string, eventInnerStyle: object, dataset: object, solidBar: Boolean, bodyColor: string, showBullet: Boolean } }) => DomConfig|DomConfig[]|string|void)|string
@@ -909,12 +909,6 @@ defineProps<{
      * Programmatic control over how many columns to span when used in a grid layout.
      */
     span ? : number
-    /**
-     * Set to `true` to stack multi-day events within each cell in the order of their start time.
-     * ...
-     * [View online docs...](https://bryntum.com/products/calendar/docs/api/Calendar/widget/YearView#config-stackMultiDayEvents)
-     */
-    stackMultiDayEvents ? : Boolean
     /**
      * This value can be one of the following:
      * ...
@@ -1601,7 +1595,6 @@ const widgetData = {
         'shortDateTimeFormat',
         'showEvents',
         'span',
-        'stackMultiDayEvents',
         'strictRecordMapping',
         'syncCalendarDate',
         'syncViewDate',

package/src/components/BryntumYearViewProps.ts

@@ -401,7 +401,7 @@ export declare type BryntumYearViewProps = {
      * @param {object} detail.renderData.dataset An object which produces the `dataset` of the resulting event bar
      * @param {boolean} detail.renderData.solidBar This is valid for views which create event bars. This is set to `true` by default for all day and interday events so that these appear as a solid block of background color. An eventRenderer may mutate this flag to change in what manner the event bar is colored - as a solid bar of color, or using the foreground color (text and icons) such as the MonthView, the CalendarRow (all day events in a DayView), and OverflowPopups
      * @param {string} detail.renderData.bodyColor When used in a [DayView](https://bryntum.com/products/calendar/docs/api/Calendar/widget/DayView), this color is applied to the body of the event element. Note that this must be light enough that the text color (From the SASS variable `$dayview-event-color`) is visible
-     * @param {boolean} detail.renderData.showBullet If there is no `iconCls`, and the event is not recurring, then by default a "bullet" circular icon is shown if the view's [showBullet](https://bryntum.com/products/calendar/docs/api/Calendar/widget/mixin/CalendarMixin#config-showBullet) if set. Setting this property in an event renderer overrides this behaviour.
+     * @param {boolean} detail.renderData.showBullet If there is no `iconCls`, and the event is not recurring, then by default a "bullet" circular icon is shown if the view's [showBullet](https://bryntum.com/products/calendar/docs/api/Calendar/widget/mixin/CalendarMixin#config-showBullet) if set. Setting this property in an event renderer overrides this behaviour. <h3>Using JSX (React)</h3> When using the Bryntum React wrapper, the event renderer can return JSX elements: ```javascript eventRenderer({ eventRecord, renderData }) {     return &lt;MyEventComponent event={eventRecord} />; } ``` *Using JSX in the event renderer creates a React portal for each rendered event. For calendars with many visible events or frequently re-rendered views, this may impact scrolling performance compared to returning plain strings or [DomConfig](https://bryntum.com/products/calendar/docs/api/Core/helper/DomHelper#typedef-DomConfig) objects. Consider using JSX primarily for events that require complex interactive React components.*
      * @returns {DomConfig,DomConfig[],string,void} The content to be used as the event body.
      */
     eventRenderer ? : ((detail: { view: CalendarView, eventRecord: EventModel, resourceRecord: ResourceModel, renderData: { style: object, cls: object, iconStyle: object, iconCls: object, eventColor: string, eventBackground: string, textColor: string, eventInnerStyle: object, dataset: object, solidBar: Boolean, bodyColor: string, showBullet: Boolean } }) => DomConfig|DomConfig[]|string|void)|string
@@ -895,12 +895,6 @@ export declare type BryntumYearViewProps = {
      * Programmatic control over how many columns to span when used in a grid layout.
      */
     span ? : number
-    /**
-     * Set to `true` to stack multi-day events within each cell in the order of their start time.
-     * ...
-     * [View online docs...](https://bryntum.com/products/calendar/docs/api/Calendar/widget/YearView#config-stackMultiDayEvents)
-     */
-    stackMultiDayEvents ? : Boolean
     /**
      * This value can be one of the following:
      * ...