Samples:
Current results:
NestedItemis rendered 3 times.NestedItemContentis rendered 9 times.ItemContentis rendered 2 times.
Expected results:
NestedItemis only rendered once.NestedItemContentis only rendered once.ItemContentis not rendered. It should only be rendered whenItem 2is selected.
Additional information:
- OK in 24.1 - CodeSandBox
Workaround
If your React Component is defined within a component that supports templates (Popup, Splitter, etc.), you can relocate the Compoent to its ***Render or ***Component props to prevent unnecessary re-rendering.
"OK in 23.1" => should be 24.1 (CodeSandBox uses the correct version)
I fixed this part. Thank you for pointing it out.
Also waiting on a solution for this. Just migrated to 24.2, and everything broke. Turns out components were rendering multiple times. Downgrading DevExtreme to previous version solved it. Awaiting solution.
Hello,
Can I kindly ask if this is being treated with enough priority? It is now two months, and it surprises me that the release is available to the general public. As it is, the product is not stable under version 24.2.
Do you have an ETA for a fix?
To me, it is clear the suggested workaround you mention does not work for all components. One example, the Drawer component.
Thank you in advance
André
Hello,
I am writing to you with concern as it has been some time since I reported stability issues with product version 24.2. I am particularly concerned to see that this version is still available to the general public despite the persistent issues.
I must stress that this issue requires an urgent solution as the suggested workaround is not solving the problems we are facing. Could you please advise me if you are giving this issue the necessary priority and provide me with an estimated date for the final fix? The current situation is significantly impacting our operations.
I thank you in advance for your prompt attention to this critical issue.
Kind regards,
Stella
Hi!
It's sad not to receive any response or feedback on the subject
Hello,
Thank you for your patience.
I understand how this issue is affecting the performance and functionality of your applications in version 24.2. Unfortunately, I don’t have additional recommendations or workarounds beyond those I mentioned earlier. However, I have escalated your requests to my team and asked them to increase its priority. The resolution was delayed due to the complexity of the issue, which affects multiple mechanisms. But we will do our best to resolve this issue as soon as possible.
Thank you once again for your patience.
Hello!
We have been waiting for a long time for an answer on this issue, I think it is taking too long… It is important to be able to solve it as soon as possible, we cannot create an unstable version…
Please, give information about how this issue is going
Hello,
we are also looking for a fix for this issue. Version 24.2 is now completely unusable in larger projects.
This needs to be fixed as soon as possible, I need version 24.2 because I am using the “Pagination” component. I cannot use another version for this reason. But as this is a paid library, no unstable versions should be created… It is normal that there are some errors, but this one in particular is a quite serious performance problem…
Just an fyi that i am experiencing issues with datagrids placed inside an <Item> within a <Box> component. The datagrids are rendering over and over again up to over 20 times, and each time a full retrieval occurs from the underlying datasource. When i moved the same datagrid outside of the box, it no longer rendered over 20 times…so it looks like this is another byproduct of the re-rending issue identified in this ticket. Awaiting a fix. thanks.
The issue is generalized, it's not one set of components, it's everything. I'm still amazed the 24.2v is open to download, at least with React, it's just broken. The workaround they mention works just for a few components, there is no general workaround. Also, for big applications, expecting people to go around applying workarounds makes no sense.
I'm DevExpress/DevExtreme user for roughly 15 years, it's the first time I see something like this, a ticket open for more then 2 months now, for a complete broken suit.
Hi!
It's sad that this was released in this state!
No answers for this thread yet, but this is a serious performance issue. We need answers or dates to base this on so we can have an update to resolve this.
Not sure, if this is a workaround, but editing source code in "node_modules/devextreme-react/esm/core/component-base.js" did some work.
node_modules/devextreme-react/esm/core/component-base.js, line 307, col 122
replaced
_renderChildren()by an empty arrayreturn (React.createElement(RestoreTreeContext.Provider, { value: restoreTree }, React.createElement(TemplateDiscoveryContext.Provider, { value: { discoveryRendering: false } }, createPortal(React.createElement(TemplateDiscoveryContext.Provider, { value: { discoveryRendering: true } }, []/*_renderChildren() replaced by an empty array*/), templateContainer), React.createElement("div", { ...getElementProps() }, React.createElement(NestedOptionContext.Provider, { value: context }, renderContent()), React.createElement(TemplateManager, { init: setTemplateManagerHooks, onTemplatesRendered: onTemplatesRendered }), isPortalComponent && React.createElement(NestedOptionContext.Provider, { value: context }, renderPortal())))));Deep test is required, but works for me at least.
Remove bundler's cache before try.
I am using
vite, and just removednode_modules/.vite/depsdirectory before test.Just checking if any update on a fix making it's way into a release soon ? thanks.
Hello,
We identified a solution to the issue and are currently running final tests before we can integrate it. If all goes well, we'll release the patch next week. I will inform you if there are any changes.