Plate 27 silently drops plugins and readonly props

[OliverWales]

Hi, as of v27 is appears that it is now required to pass plugins and readonly state directly to <Plate />? Previously we instantiated the editor with the plugins and readonly and then passed just the editor to <Plate /> but now unless we also pass the plugins explicitly then none of the jotai providers (TableProvider etc.) are rendered. Feels like a bug/regression?

[12joan]

Hi Oli,

We upgraded jotai from v1 to v2 as part of that release, and the behaviour of some stores (including the one used by <Plate /> may have changed as a result. Dropping support for passing plugins via the editor object wasn't our intention, but it sounds like that was a side effect of those changes.

I recommend switching to passing plugins directly to <Plate />, which is the standard way of passing plugins and is much less likely to break.

[OliverWales]

Would've been nice to note this in the patch notes / breaking changes, especially given it also affects readonly meaning it silently made all of our readonly editors behave as if they were editable 🙃

Now passing plugins by that method but nothing in the types indicates that it is required.

[12joan]

CC @zbeyens

The readOnly issue is also affecting the disabled editor example on the docs site. It looks like previously, setting readOnly on PlateContent was enough to make the editor read-only, but now readOnly must be set on Plate instead.

@zbeyens Any idea what might have caused this regression?

[12joan]

@OliverWales We've figured out the cause of both issues. They should be fixed in this PR.
#2822

[OliverWales]

Brill, thank you!