[REACT] Thin - subGridConfigs usage causes fatal error

[a.newteam]

Hello Bryntum Team,

I am encountering an issue with the code provided in the property booking example. I am having trouble getting the subGridConfigs usage to function correctly. When the key is present in the scheduler props, it causes the page to break. Additionally, I noticed that the key is only used in the config file, not in the JSX above the DOM tree.

I have created a screen share to demonstrate the problem. You can view it below.

Screen Share:
https://app.gemoo.com/share/home?codeId=M0aVWJAVoQRNY

Could you please take a look at the error message that is being thrown? I am not certain if this information will be useful, but I am hoping that someone can assist me in identifying any mistakes I may have made or if there is a bug in the library itself.

Thank you in advance.

Uncaught Error: Id b-scheduler-1-lockedSubgrid already in use
    at SubGrid.registerInstance (chunk-X65ZTVLL.js?v=e9a6d642:12201:13)
    at SubGrid.updateId (chunk-X65ZTVLL.js?v=e9a6d642:12176:9)
    at SubGrid.updateId (chunk-PVOU4662.js?v=e9a6d642:9992:11)
    at SubGrid.set (chunk-X65ZTVLL.js?v=e9a6d642:2716:52)
    at SubGrid.get (chunk-X65ZTVLL.js?v=e9a6d642:2748:18)
    at SubGrid.changeElement (chunk-PVOU4662.js?v=e9a6d642:9547:16)
    at SubGrid.changeElement (chunk-66N2ZXM5.js?v=e9a6d642:9047:18)
    at SubGrid.set (chunk-X65ZTVLL.js?v=e9a6d642:2707:44)
    at SubGrid.get (chunk-X65ZTVLL.js?v=e9a6d642:2748:18)
    at SubGrid.getConfig (chunk-X65ZTVLL.js?v=e9a6d642:3824:21)

[marcio]

Hello a.newteam,

Thanks for reaching out.

I checked your video, just to confirm, in your columns, do you have any column assigned to the left region?

Also, is the demo that you mentioned this one? https://bryntum.com/products/scheduler/examples/booking/

If you could provide a runnable test case for us to debug, that would be great and would help us identify what is causing that error.

[a.newteam]

Hi Marco!

Yes that is the correct example I am using.

No my columns are set up like this:

 columns: [
      {
        type: 'tree',
        text: 'Venue',
        field: 'name',
        sum: 'count',
        summaryRenderer: ({ sum }) => StringHelper.xss`Total Spaces: ${sum}`,
        showMeta: (resource: SpaceModel) => {
          const icon =
            resource.occupancy < 25 ? 'user' : resource.occupancy < 200 ? 'user-friends' : 'users';
          return `${StringHelper.encodeHtml(resource.occupancy.toString())}<div class="capacity !pr-4 b-fa b-fa-${icon}"></div>`;
        },
      },
    ],

I can see about providing an example.

[marcio]

Hey,

Thanks for sharing that.

It seems that the problem is not with the column definition, but you can try to set it to the left section just to confirm.

We'll need a test case to debug and identify what's happening there, you can get one of our demos, then adapt it to match your configuration, or have the error happening, then send it back to us here in the forums.

We'll be waiting for that.