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

Don't send displayModel to "rendering" components on server side #4518

Merged
merged 2 commits into from
Aug 15, 2024

Conversation

cmdcolin
Copy link
Collaborator

In the past, the displayModel was snapshotted and only 'selectedFeatureId' was sent to the backend. This was with the 'intent' to make the server side render the 'selected' feature border, or highlight.

However, this was found to result in hydration mismatch errors, so was removed, but displayModel is still forwarded to the server side. This changes it to nullify the displayModel attribute, and then corrects typescript attributes in the "rendering" components to make this more clear

this PR is made because the no-unnecessary-condition rule benefits from correct knowledge of the types

@cmdcolin cmdcolin changed the title Don't send displayModel to "rendering" components Don't send displayModel to "rendering" components on server side Aug 15, 2024
@cmdcolin cmdcolin merged commit 317644a into main Aug 15, 2024
9 checks passed
@cmdcolin cmdcolin deleted the fix_displaymodel branch August 15, 2024 17:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant