Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix "dot-separated" paths by making paths type string[] (instead of string) #1862

Closed

Conversation

mirismaili
Copy link
Contributor

@mirismaili mirismaili commented Dec 29, 2021

Fix "dot-separated" paths by making paths type string[] (instead of string) for react (in these packages: "core", "react" and "material-renderers")

#1849
#1831

@mirismaili
Copy link
Contributor Author

I know this can't be merged now. Because of conflicts with unfixed packages (angular, vue, ...). But those can be fixed, as well.

@sdirix
Copy link
Member

sdirix commented Jan 3, 2022

Hi @mirismaili, thanks for the PR. We're already working on this, see #1831

The main problem with the array approach is to not lose performance. Just replacing strings with arrays here will lead to massive degradation as the memoization of React will no longer work and therefore the whole form will rerender with every change.

… `string`) for react (in these packages: "core", "react" and "material-renderers")

eclipsesource#1849
eclipsesource#1831
@lepffm
Copy link

lepffm commented May 18, 2023

Hi, Has the "dot-seperated" issue been resolved yet?

@sdirix
Copy link
Member

sdirix commented Jun 29, 2023

We came up with a better solution, documented it in #2153 and will start developing it soon. Therefore I'll close this PR as it's outdated.

@sdirix sdirix closed this Jun 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants