@bryntum/calendar-vue-3 7.2.0 → 7.2.2

package/src/components/BryntumCombo.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/Core/widget/Combo#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/BryntumComboProps.ts

@@ -175,7 +175,7 @@ export declare type BryntumComboProps = {
     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/Core/widget/Combo#config-createOnUnmatched)
@@ -670,7 +670,7 @@ export declare type BryntumComboProps = {
     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/BryntumDateField.vue

@@ -546,7 +546,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/BryntumDateFieldProps.ts

@@ -532,7 +532,7 @@ export declare type BryntumDateFieldProps = {
     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/BryntumDateRangeField.vue

@@ -557,7 +557,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/BryntumDateRangeFieldProps.ts

@@ -543,7 +543,7 @@ export declare type BryntumDateRangeFieldProps = {
     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/BryntumDateTimeField.vue

@@ -478,7 +478,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/BryntumDateTimeFieldProps.ts

@@ -464,7 +464,7 @@ export declare type BryntumDateTimeFieldProps = {
     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/BryntumDayAgendaView.vue

@@ -503,7 +503,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/BryntumDayAgendaViewProps.ts

@@ -489,7 +489,7 @@ export declare type BryntumDayAgendaViewProps = {
      * @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/BryntumDayResourceView.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/BryntumDayResourceViewProps.ts

@@ -488,7 +488,7 @@ export declare type BryntumDayResourceViewProps = {
      * @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/BryntumDayView.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/BryntumDayViewProps.ts

@@ -488,7 +488,7 @@ export declare type BryntumDayViewProps = {
      * @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/BryntumDisplayField.vue

@@ -491,7 +491,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/BryntumDisplayFieldProps.ts

@@ -477,7 +477,7 @@ export declare type BryntumDisplayFieldProps = {
     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/BryntumDurationField.vue

@@ -531,7 +531,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/BryntumDurationFieldProps.ts

@@ -517,7 +517,7 @@ export declare type BryntumDurationFieldProps = {
     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/BryntumEditor.vue

@@ -67,7 +67,7 @@ defineProps<{
      */
     autoUpdateRecord ? : Boolean
     /**
-     * What action should be taken when focus moves out of the editor, either by `TAB` or clicking outside.
+     * What action should be taken when focus moves out of the editor, either by <kbd>Tab</kbd> or clicking outside.
      * May be `'complete'` or `'cancel`'. Any other value results in no action being taken upon focus leaving the editor
      * leaving the application to listen for the [focusOut](https://bryntum.com/products/calendar/docs/api/Core/widget/Editor#event-focusOut) event.
      */
@@ -650,7 +650,7 @@ const emit = defineEmits<{
      */
     (e: 'afterEdit', params: ((event: { source: Editor, record?: Model }) => void)|string): void
     /**
-     * Fired when cancellation has been requested, either by `ESC`, or focus loss (if configured to cancel on blur).
+     * Fired when cancellation has been requested, either by <kbd>Escape</kbd>, or focus loss (if configured to cancel on blur).
      * The cancellation may be vetoed, in which case, focus is moved back into the editor.
      * @param {string} e Event name
      * @param {object} params Event parameters
@@ -662,7 +662,7 @@ const emit = defineEmits<{
      */
     (e: 'beforeCancel', params: ((event: { oldValue: object, value: object, event: Event, source: Editor }) => Promise<boolean>|boolean|void)|string): Promise<boolean>|boolean|void
     /**
-     * Fired when an edit completion has been requested, either by `ENTER`, or focus loss (if configured to complete on blur).
+     * Fired when an edit completion has been requested, either by <kbd>Enter</kbd>, or focus loss (if configured to complete on blur).
      * The completion may be vetoed, in which case, focus is moved back into the editor.
      * @param {string} e Event name
      * @param {object} params Event parameters

package/src/components/BryntumEditorProps.ts

@@ -53,7 +53,7 @@ export declare type BryntumEditorProps = {
      */
     autoUpdateRecord ? : Boolean
     /**
-     * What action should be taken when focus moves out of the editor, either by `TAB` or clicking outside.
+     * What action should be taken when focus moves out of the editor, either by <kbd>Tab</kbd> or clicking outside.
      * May be `'complete'` or `'cancel`'. Any other value results in no action being taken upon focus leaving the editor
      * leaving the application to listen for the [focusOut](https://bryntum.com/products/calendar/docs/api/Core/widget/Editor#event-focusOut) event.
      */

package/src/components/BryntumEventColorField.vue

@@ -510,7 +510,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/BryntumEventColorFieldProps.ts

@@ -496,7 +496,7 @@ export declare type BryntumEventColorFieldProps = {
     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/BryntumEventList.vue

@@ -435,7 +435,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
@@ -854,7 +854,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/Calendar/widget/EventList#config-rowHeight)
@@ -1170,7 +1170,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)
      */
@@ -1270,8 +1270,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)
@@ -1476,7 +1476,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
@@ -2482,7 +2482,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 the range of dates encapsulated by this view changes.
      * ...
@@ -2778,6 +2778,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
@@ -3075,6 +3085,7 @@ const widgetData = {
         'onToggleGroup',
         'onToggleNode',
         'onToolClick',
+        'onTreeGroup',
         'onUnlockRows',
         'onUnsplit',
         'pastEventCls',
@@ -3247,6 +3258,7 @@ const widgetData = {
         'toggleGroup',
         'toggleNode',
         'toolClick',
+        'treeGroup',
         'unlockRows',
         'unsplit'
     ]

package/src/components/BryntumEventListProps.ts

@@ -421,7 +421,7 @@ export declare type BryntumEventListProps = {
      * @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
@@ -840,7 +840,7 @@ export declare type BryntumEventListProps = {
     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/Calendar/widget/EventList#config-rowHeight)
@@ -1156,7 +1156,7 @@ export declare type BryntumEventListProps = {
     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)
      */
@@ -1256,8 +1256,8 @@ export declare type BryntumEventListProps = {
     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/BryntumFileField.vue

@@ -502,7 +502,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/BryntumFileFieldProps.ts

@@ -488,7 +488,7 @@ export declare type BryntumFileFieldProps = {
     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/BryntumFilterField.vue

@@ -532,7 +532,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/BryntumFilterFieldProps.ts

@@ -518,7 +518,7 @@ export declare type BryntumFilterFieldProps = {
     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/BryntumGrid.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/Grid#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
@@ -2598,6 +2608,7 @@ const widgetData = {
         'onToggleGroup',
         'onToggleNode',
         'onToolClick',
+        'onTreeGroup',
         'onUnlockRows',
         'onUnsplit',
         'preserveScroll',
@@ -2747,6 +2758,7 @@ const widgetData = {
         'toggleGroup',
         'toggleNode',
         'toolClick',
+        'treeGroup',
         'unlockRows',
         'unsplit'
     ]