Dear Support,
I refer to your latest release notes which mention that fetchOptions was depreciated.
CrudManager.transport.load.fetchOptions (v5.0.0)
I can confirm that FetchOptions was working fine in the following configuration
"@bryntum/core-angular-thin": "5.6.8",
"@bryntum/core-thin": "5.6.8",
"@bryntum/engine-thin": "5.6.8",
"@bryntum/grid-thin": "5.6.8",
"@bryntum/scheduler-angular-thin": "5.6.8",
"@bryntum/scheduler-thin": "5.6.8",
"@bryntum/calendar-angular-thin": "5.6.8",
"@bryntum/calendar-thin": "5.6.8",
But it stopped working in this configuration.
"@bryntum/core-angular-thin": "6.0.0-alpha-1",
"@bryntum/core-thin": "6.0.0-alpha-1",
"@bryntum/engine-thin": "6.0.0-alpha-1",
"@bryntum/grid-thin": "6.0.0-alpha-1",
"@bryntum/scheduler-angular-thin": "6.0.0-alpha-1",
"@bryntum/scheduler-thin": "6.0.0-alpha-1",
"@bryntum/calendar-angular-thin": "6.0.0-alpha-1",
"@bryntum/calendar-thin": "6.0.0-alpha-1",
Some questions please;
What was the main reason behind this deprecation?
Is there another way to pass options in the CrudManager data loading section?
We have tried multiple ways to satisfy the requirements of this request but so far we were unsuccessful. We are committed to increasing security but also need to work around a stable live environment.
Any insights such as best practice on this issue would be appreciated.