You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using validation for a field with type colorlist and the validation fails there is a warning icon next to the field label in the studio. When hovering over the icon the studio crashes with the error Error: flushSync was called from inside a lifecycle method. It cannot be called when React is already rendering.
This can be recreated by creating a new studio with for instance the blog template. Then add the example field from the readme and add validation.
When creating a document the warning icon appears, when hovering over the icon the studio crashes.
I'm using the following versions:
@sanity/cli 2.35.0 (up to date)
@sanity/base 2.35.0 (up to date)
@sanity/core 2.35.0 (up to date)
@sanity/default-layout 2.35.0 (up to date)
@sanity/default-login 2.35.0 (up to date)
@sanity/desk-tool 2.35.1 (up to date)
@sanity/eslint-config-studio 2.0.1 (up to date)
@sanity/vision 2.35.0 (up to date)
Node and npm
v16.17.0
8.19.2
The text was updated successfully, but these errors were encountered:
Not sure if this applies to everyone, but we noticed that this bug only happens in development. It is still annoying and confusing, but at least does prevent the lib from being used successfully in production.
When using validation for a field with type
colorlist
and the validation fails there is a warning icon next to the field label in the studio. When hovering over the icon the studio crashes with the errorError: flushSync was called from inside a lifecycle method. It cannot be called when React is already rendering.
This can be recreated by creating a new studio with for instance the blog template. Then add the example field from the readme and add validation.
When creating a document the warning icon appears, when hovering over the icon the studio crashes.
I'm using the following versions:
Node and npm
The text was updated successfully, but these errors were encountered: