@bryntum/schedulerpro-vue-3-thin 7.2.3 → 7.3.0

package/src/components/BryntumSchedulerProProjectModel.vue

@@ -23,16 +23,14 @@ defineProps<{
      * If this flag is set to `true` (default) when a start/end date is set on the event, a corresponding
      * `start-no-earlier/later-than` constraint is added, automatically. This is done in order to
      * keep the event "attached" to this date, according to the user intention.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-addConstraintOnDateSet)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-addConstraintOnDateSet)
      */
     addConstraintOnDateSet ? : Boolean
     /**
      * This config manages DST correction in the scheduling engine. It only has effect when DST transition hour is
      * working time. Usually a DST transition occurs on a Sunday, so with non-working weekends the DST correction logic
      * is not involved.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-adjustDurationToDST)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-adjustDurationToDST)
      */
     adjustDurationToDST ? : Boolean
     /**
@@ -68,8 +66,7 @@ defineProps<{
     autoCalculatePercentDoneForParentTasks ? : Boolean
     /**
      * Specify `true` to automatically call [load](https://bryntum.com/products/schedulerpro/docs/api/Scheduler/crud/AbstractCrudManagerMixin#function-load) method on the next frame after creation.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-autoLoad)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-autoLoad)
      */
     autoLoad ? : Boolean
     /**
@@ -90,8 +87,7 @@ defineProps<{
     /**
      * An object where property names with a truthy value indicate which events should bubble up the ownership
      * hierarchy when triggered.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-bubbleEvents)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-bubbleEvents)
      */
     bubbleEvents ? : object
     /**
@@ -125,46 +121,39 @@ defineProps<{
     calendarsData ? : CalendarModel[]
     /**
      * Set to `true` to call onXXX method names (e.g. `onShow`, `onClick`), as an easy way to listen for events.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-callOnFunctions)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-callOnFunctions)
      */
     callOnFunctions ? : Boolean
     /**
      * By default, if an event handler throws an exception, the error propagates up the stack and the
      * application state is undefined. Code which follows the event handler will *not* be executed.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-catchEventHandlerExceptions)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-catchEventHandlerExceptions)
      */
     catchEventHandlerExceptions ? : Boolean
     /**
      * Child nodes. To allow loading children on demand, specify `children : true` in your data. Omit the field for leaf
      * tasks.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-children)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-children)
      */
     children ? : Boolean|object[]|Model[]|ModelConfig[]
     /**
      * Sets the list of stores controlled by the CRUD manager.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-crudStores)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-crudStores)
      */
     crudStores ? : Store[]|string[]|CrudManagerStoreDescriptor[]|StoreConfig[]
     /**
      * The number of days per month.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-daysPerMonth)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-daysPerMonth)
      */
     daysPerMonth ? : number
     /**
      * The number of days per week.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-daysPerWeek)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-daysPerWeek)
      */
     daysPerWeek ? : number
     /**
      * Enables early rendering in SchedulerPro, by postponing calculations to after the first refresh.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-delayCalculation)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-delayCalculation)
      */
     delayCalculation ? : Boolean
     /**
@@ -175,8 +164,7 @@ defineProps<{
     /**
      * The source of the calendar for dependencies (the calendar used for taking dependencies lag into account).
      * Possible values are:
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-dependenciesCalendar)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-dependenciesCalendar)
      */
     dependenciesCalendar ? : 'ToEvent'|'FromEvent'|'Project'
     /**
@@ -203,16 +191,14 @@ defineProps<{
     /**
      * Set to `true` to enable calculation progress notifications.
      * When enabled the project fires [progress](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#event-progress) event.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-enableProgressNotifications)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-enableProgressNotifications)
      */
     enableProgressNotifications ? : Boolean
     /**
      * Configuration of the JSON encoder used by the *Crud Manager*.
+     * @property {object} encoder.requestData Static data to send with the data request. ```javascript new CrudManager({     // add static "foo" property to all requests data     encoder : {         requestData : {             foo : 'Bar'         }     },     ... }); ``` The above snippet will result adding "foo" property to all requests data: ```json     {         "requestId"   : 756,         "type"        : "load",          "foo"         : "Bar",          "stores"      : [             ... ```
      */
-    encoder ? : {
-        requestData?: object
-    }
+    encoder ? : { requestData: object }
     /**
      * The constructor of the event model class, to be used in the project. Will be set as the
      * [modelClass](https://bryntum.com/products/schedulerpro/docs/api/Core/data/Store#config-modelClass) property of the [eventStore](#SchedulerPro/model/ProjectModel#property-eventStore)
@@ -249,15 +235,13 @@ defineProps<{
     forceSync ? : Boolean
     /**
      * The number of hours per day.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-hoursPerDay)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-hoursPerDay)
      */
     hoursPerDay ? : number
     /**
      * Unique identifier for the record. Might be mapped to another dataSource using idField, but always exposed as
      * record.id. Will get a generated value if none is specified in records data.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-id)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-id)
      */
     id ? : string|number
     /**
@@ -268,8 +252,7 @@ defineProps<{
     /**
      * Set to `false` to only include the id of a removed parent node in the request to the backend (also
      * affects programmatic calls to get [changes](https://bryntum.com/products/schedulerpro/docs/api/Scheduler/crud/AbstractCrudManagerMixin#property-changes) etc.), and not the ids of its children.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-includeChildrenInRemoveRequest)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-includeChildrenInRemoveRequest)
      */
     includeChildrenInRemoveRequest ? : Boolean
     /**
@@ -284,14 +267,12 @@ defineProps<{
      * [lazyLoad](https://bryntum.com/products/schedulerpro/docs/api/Core/data/Store#config-lazyLoad). If set on a parent record at load time, that parent will not cause any
      * more child load requests. If omitted, it will be automatically set to `true` when a load request receives fewer
      * child records than requested.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-isFullyLoaded)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-isFullyLoaded)
      */
     isFullyLoaded ? : Boolean
     /**
      * Project data as a JSON string, used to populate its stores.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-json)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-json)
      */
     json ? : string
     /**
@@ -303,25 +284,22 @@ defineProps<{
      * @param {DurationUnit} bufferUnit Used together with bufferAmount to calculate the start and end dates of each load request. The value is added to the current visible start or end date. Defaults to the visible time span length (does not affect ResourceStore).
      * @param {number} bufferAmount See `bufferUnit`
      */
-    lazyLoad ? : Boolean|{lazyLoad: { chunkSize: number }, bufferUnit: DurationUnit, bufferAmount: number}
+    lazyLoad ? : Boolean|{ lazyLoad: { chunkSize: number }, bufferUnit: DurationUnit, bufferAmount: number }
     /**
      * The listener set for this object.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-listeners)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-listeners)
      */
     listeners ? : ProjectModelListeners
     /**
      * Convenience shortcut to set only the url to load from, when you do not need to supply any other config
      * options in the `load` section of the `transport` config.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-loadUrl)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-loadUrl)
      */
     loadUrl ? : string
     /**
      * Maximum range the project calendars can iterate.
      * The value is defined in milliseconds and by default equals `5 years` roughly.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-maxCalendarRange)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-maxCalendarRange)
      */
     maxCalendarRange ? : number
     /**
@@ -360,15 +338,13 @@ defineProps<{
      * Setting this to `true` (default) vetoes [silenceInitialCommit](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-silenceInitialCommit) effect
      * by preventing silent changes accepting
      * on initial data loading if some scheduling issue gets resolved during it.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-preventSilencingOnIssueResolve)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-preventSilencingOnIssueResolve)
      */
     preventSilencingOnIssueResolve ? : Boolean
     /**
      * Flag the record as read-only on the UI level, preventing the end user from manipulating it using editing
      * features such as cell editing and event dragging.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-readOnly)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-readOnly)
      */
     readOnly ? : Boolean
     /**
@@ -382,16 +358,14 @@ defineProps<{
      * If set to `true`, this makes the CrudManager load pages of data, instead of loading the complete dataset at
      * once. The requests made to the [loadUrl](https://bryntum.com/products/schedulerpro/docs/api/Scheduler/crud/AbstractCrudManagerMixin#config-loadUrl) will contain
      * params with info about the current dataset being requested:
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-remotePaging)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-remotePaging)
      */
     remotePaging ? : Boolean
     /**
      * When the CrudManager/Project is configured with [lazyLoad](https://bryntum.com/products/schedulerpro/docs/api/Scheduler/crud/mixin/LazyLoadCrudManager#config-lazyLoad) set to `true`, you can configure
      * your own data fetching logic by implementing this function. Doing this will override the built-in fetching
      * mechanism using the [loadUrl](https://bryntum.com/products/schedulerpro/docs/api/Scheduler/data/CrudManager#config-loadUrl).
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-requestData)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-requestData)
      * @param {LazyLoadCrudManagerRequestParams} params Object containing info of what data is requested
      * @returns {CrudManagerRequestResponse}
      */
@@ -463,8 +437,7 @@ defineProps<{
      * Experimental hook that lets the app determine if a bound dataset needs syncing with the store or not, and
      * if it does - which records that should be processed. Only called for stores that are configured with
      * `syncDataOnLoad: true` (which is the default in the React, Angular and Vue wrappers).
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-shouldSyncDataOnLoad)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-shouldSyncDataOnLoad)
      * @param {object} options Options passed by the store to this hook
      * @param {Core.data.Store} options.store Store about to be synced
      * @param {Core.data.Model} options.records Records currently in the store
@@ -474,22 +447,19 @@ defineProps<{
     shouldSyncDataOnLoad ? : (options: { store: Store, records: Model, data: object[] }) => Set<any>|Boolean
     /**
      * Silences propagations caused by the project loading.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-silenceInitialCommit)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-silenceInitialCommit)
      */
     silenceInitialCommit ? : Boolean
     /**
      * When `true` the project's manually scheduled tasks duration will include only working periods of time.
      * When `false` such tasks will ignore working time calendars and treat all intervals as working.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-skipNonWorkingTimeInDurationWhenSchedulingManually)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-skipNonWorkingTimeInDurationWhenSchedulingManually)
      */
     skipNonWorkingTimeInDurationWhenSchedulingManually ? : Boolean
     /**
      * When `true` the project's manually scheduled tasks will adjust their proposed start/end dates to skip non-working
      * time.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-skipNonWorkingTimeWhenSchedulingManually)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-skipNonWorkingTimeWhenSchedulingManually)
      */
     skipNonWorkingTimeWhenSchedulingManually ? : Boolean
     /**
@@ -506,30 +476,26 @@ defineProps<{
      * store to use it by id. Store identifier is used as a container name holding corresponding store data
      * while transferring them to/from the server. By default, `id` property is used. And in case a
      * container identifier has to differ this config can be used:
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-storeIdProperty)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-storeIdProperty)
      */
     storeIdProperty ? : string
     /**
      * When `true` the Crud Manager does not require all updated and removed records to be mentioned in the
      * *sync* response. In this case response should include only server side changes.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-supportShortSyncResponse)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-supportShortSyncResponse)
      */
     supportShortSyncResponse ? : Boolean
     /**
      * An array of store identifiers sets an alternative sync responses apply order.
      * By default, the order in which sync responses are applied to the stores is the same as they
      * registered in. But in case of some tricky dependencies between stores this order can be changed:
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-syncApplySequence)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-syncApplySequence)
      */
     syncApplySequence ? : string[]|CrudManagerStoreDescriptor[]
     /**
      * Convenience shortcut to set only the url to sync to, when you do not need to supply any other config
      * options in the `sync` section of the `transport` config.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-syncUrl)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-syncUrl)
      */
     syncUrl ? : string
     /**
@@ -560,14 +526,12 @@ defineProps<{
      * Set to a IANA time zone (i.e. `Europe/Stockholm`) or a UTC offset in minutes (i.e. `-120`). This will
      * convert all events, tasks and time ranges to the specified time zone or offset. It will also affect the
      * displayed timeline's headers as well at the start and end date of it.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-timeZone)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-timeZone)
      */
     timeZone ? : string|number
     /**
      * Specifies the output format of [toJSON](https://bryntum.com/products/schedulerpro/docs/api/Scheduler/model/mixin/ProjectModelCommon#function-toJSON).
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-toJSONResultFormat)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-toJSONResultFormat)
      */
     toJSONResultFormat ? : 'inlineData'|'model'
     /**
@@ -584,28 +548,34 @@ defineProps<{
     trackResponseType ? : Boolean
     /**
      * Configuration of the AJAX requests used by *Crud Manager* to communicate with a server-side.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-transport)
-     */
-    transport ? : {
-        load?: object
-        sync?: object
-    }
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-transport)
+     * @property {object} [transport.load] Load requests configuration:
+     * @property {string} [transport.load.url] URL to request for data loading.
+     * @property {string} [transport.load.method] HTTP method to be used for load requests.
+     * @property {string} [transport.load.paramName] Name of the parameter that will contain a serialized `load` request. The value is mandatory for requests using `GET` method (default for `load`) so if the value is not provided `data` string is used as default. This value is optional for HTTP methods like `POST` and `PUT`, the request body will be used for data transferring in these cases.
+     * @property {object} [transport.load.params] An object containing extra HTTP parameters to pass to the server when sending a `load` request. ```javascript transport : {     load : {         url       : 'http://mycool-server.com/load.php',         // HTTP request parameter used to pass serialized "load"-requests         paramName : 'data',         // pass extra HTTP request parameter         // so resulting URL will look like: http://mycool-server.com/load.php?userId=123456&data=...         params    : {             userId : '123456'         }     },     ... } ```
+     * @property {Record<string, string>} [transport.load.headers] An object containing headers to pass to each server request. ```javascript transport : {     load : {         url       : 'http://mycool-server.com/load.php',         // HTTP request parameter used to pass serialized "load"-requests         paramName : 'data',         // specify Content-Type for "load" requests         headers   : {             'Content-Type' : 'application/json'         }     },     ... } ```
+     * @property {object} [transport.sync] Sync requests (`sync` in further text) configuration:
+     * @property {string} [transport.sync.url] URL to request for `sync`.
+     * @property {string} [transport.sync.method] HTTP request method to be used for `sync`.
+     * @property {string} [transport.sync.paramName] Name of the parameter in which `sync` data will be transferred. This value is optional for requests using methods like `POST` and `PUT`, the request body will be used for data transferring in this case (default for `sync`). And the value is mandatory for requests using `GET` method (if the value is not provided `data` string will be used as fallback).
+     * @property {object} [transport.sync.params] HTTP parameters to pass with an HTTP request handling `sync`. ```javascript transport : {     sync : {         url    : 'http://mycool-server.com/sync.php',         // extra HTTP request parameter         params : {             userId : '123456'         }     },     ... } ```
+     * @property {Record<string, string>} [transport.sync.headers] HTTP headers to pass with an HTTP request handling `sync`. ```javascript transport : {     sync : {         url     : 'http://mycool-server.com/sync.php',         // specify Content-Type for "sync" requests         headers : {             'Content-Type' : 'application/json'         }     },     ... } ```
+     */
+    transport ? : { load?: { url?: string, method?: string, paramName?: string, params?: object, headers?: Record<string, string> }, sync?: { url?: string, method?: string, paramName?: string, params?: object, headers?: Record<string, string> } }
     /**
      * By default, the stores of a project use the raw data objects passed to them as the data source for their
      * records if data is loaded remotely (using an `AjaxStore` or a `CrudManager`). For data supplied inline,
      * the data objects are instead by default cloned to avoid the original data object being modified by the
      * store.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-useRawData)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-useRawData)
      */
     useRawData ? : Boolean
     /**
      * This config validates the response structure for requests made by the Crud Manager.
      * When `true`, the Crud Manager checks every parsed response structure for errors
      * and if the response format is invalid, a warning is logged to the browser console.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-validateResponse)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#config-validateResponse)
      */
     validateResponse ? : Boolean
     /**
@@ -669,8 +639,7 @@ const emit = defineEmits<{
     (e: 'beforeResponseApply', params: ((event: { source: AbstractCrudManager, requestType: 'sync'|'load', response: object }) => Promise<boolean>|boolean|void)|string): Promise<boolean>|boolean|void
     /**
      * Fires before a request is sent to the server.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#event-beforeSend)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#event-beforeSend)
      * @param {string} e Event name
      * @param {object} params Event parameters
      * @param {string} params.e Event name
@@ -684,8 +653,7 @@ const emit = defineEmits<{
     (e: 'beforeSend', params: ((event: { crudManager: AbstractCrudManager, params: object, requestType: 'sync'|'load', requestConfig: object }) => Promise<void>)|string): Promise<void>
     /**
      * Fires before [sync request](https://bryntum.com/products/schedulerpro/docs/api/Scheduler/crud/AbstractCrudManagerMixin#function-sync) is sent. Return `false` to cancel sync request.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#event-beforeSync)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#event-beforeSync)
      * @param {string} e Event name
      * @param {object} params Event parameters
      * @param {string} params.e Event name
@@ -709,8 +677,7 @@ const emit = defineEmits<{
     (e: 'beforeSyncApply', params: ((event: { source: AbstractCrudManager, response: object }) => Promise<boolean>|boolean|void)|string): Promise<boolean>|boolean|void
     /**
      * Fires when any other event is fired from the object.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#event-catchAll)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#event-catchAll)
      * @param {string} e Event name
      * @param {object} params Event parameters
      * @param {string} params.e Event name
@@ -722,8 +689,7 @@ const emit = defineEmits<{
     (e: 'catchAll', params: ((event: {[key: string]: any, type: string}) => void)|string): void
     /**
      * Fired when data in any of the projects stores changes.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#event-change)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#event-change)
      * @param {string} e Event name
      * @param {object} params Event parameters
      * @param {string} params.e Event name
@@ -753,8 +719,7 @@ const emit = defineEmits<{
     (e: 'cycle', params: ((event: { schedulingIssue: { getDescription: Function, cycle: object, getResolutions: Function }, continueWithResolutionResult: Function }) => void)|string): void
     /**
      * Fired when the engine has finished its calculations and the results has been written back to the records.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#event-dataReady)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#event-dataReady)
      * @param {string} e Event name
      * @param {object} params Event parameters
      * @param {string} params.e Event name
@@ -792,8 +757,7 @@ const emit = defineEmits<{
     (e: 'emptyCalendar', params: ((event: { schedulingIssue: { getDescription: Function, getCalendar: Function, getResolutions: Function }, continueWithResolutionResult: Function }) => void)|string): void
     /**
      * Fires when data in any of the registered data stores is changed.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#event-hasChanges)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#event-hasChanges)
      * @param {string} e Event name
      * @param {object} params Event parameters
      * @param {string} params.e Event name
@@ -847,8 +811,7 @@ const emit = defineEmits<{
      * Fires when registered stores get into state when they don't have any
      * not persisted change. This happens after [load](https://bryntum.com/products/schedulerpro/docs/api/Scheduler/crud/AbstractCrudManagerMixin#function-load) or [sync](#Scheduler/crud/AbstractCrudManagerMixin#function-sync) request
      * completion. Or this may happen after a record update which turns its fields back to their original state.
-     * ...
-     * [View online docs...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#event-noChanges)
+     * [More...](https://bryntum.com/products/schedulerpro/docs/api/SchedulerPro/model/ProjectModel#event-noChanges)
      * @param {string} e Event name
      * @param {object} params Event parameters
      * @param {string} params.e Event name
@@ -910,7 +873,7 @@ const emit = defineEmits<{
      * @param {object} params.params Event parameters
      * @param {object} params.params.event Event object
      * @param {string} params.params.event.localRevisionId ID of the local revision. Backend should send it in the broadcast channel
-     * @param {string} params.params.event.conflictResolutionFor ID of the revision with a conflict which was resolved by this revision
+     * @param {string} [params.params.event.conflictResolutionFor] ID of the revision with a conflict which was resolved by this revision
      * @param {string} params.params.event.clientId ID of the client instance. Used to distinguish own revisions from the broadcast channel
      * @param {object} params.params.event.changes Object with changes constituting revision
      */
@@ -1116,16 +1079,9 @@ const widgetData = {
         'trackProjectModelChanges'
     ],
     propertyNames : [
-        'allChildren',
-        'allUnfilteredChildren',
         'descendantCount',
-        'hasGeneratedId',
         'inlineData',
-        'internalId',
-        'isCommitting',
         'isCreating',
-        'isValid',
-        'previousSiblingsTotalCount',
         'segmentModelClass',
         'visibleDescendantCount'
     ],