-
Notifications
You must be signed in to change notification settings - Fork 40
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
Editorjs instance does not update when interface value changes #45
Comments
Would you like to contribute that PR to the community? There are recent requests #48 to keep this extensions on par with upstream, whyfore a little activity around the edges could help to revive a healthy social environment for the code. |
I had successfully forgotten about this issue. Will pull up the commits we did and do a PR in the coming days |
Many thanks in advance!
…On Fri, 14 Apr 2023 at 07:46, Augusts Kārkliņš ***@***.***> wrote:
Would you like to contribute that PR to the community?
There are recent requests #48
<#48>
to keep this extensions on par with upstream, whyfore a little activity
around the edges could help to revive a healthy social environment for the
code.
I had successfully forgotten about this issue. Will pull up the commits we
did and do a PR in the coming days
—
Reply to this email directly, view it on GitHub
<#45 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMRV7CBH6HQZNQQT2ERQPTXBDQBVANCNFSM6AAAAAARP3MPP4>
.
You are receiving this because you commented.Message ID:
<dimitrov-adrian/directus-extension-editorjs-interface/issues/45/1507953745
@github.com>
|
Hi
First of all, big thanks for making this interface, it's really helpful for our Directus use case.
Second, I'd like to point out a bug we encountered. It seems that editorjs is not re-rendered when the value of interface changes, for example:
I've tracked it down to this commit.
It looks like emitValue and watch conflict with one another. emitValue is fired when editorjs initializes and marks
isInternalChange
as true, but it never resets it back.A way to fix this would be to:
isInternalChange
back to false, if it encounters itfinally
to emiValue promise returned that changesisInternalChange
back to falseThis is what we've done on our forked version of this interface to fix it for us. I'm happy to make PR here as well if necessary
The text was updated successfully, but these errors were encountered: