Modify v-editable directive to react to data changes #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes an issue that I encountered using nuxt full-static preview mode where my site loads the baked "published" storyblok json without the _editable fields on first open. When the nuxt preview mode re-fetches the live "draft" data, the
v-editable
directive has already run the bind function and does not set the required data attributes. This change makes thev-editable
directive react to changes in the _editable data and will only run when the data has changed.This also avoids having to use hacks like this (which also introduce a flash of content and dom rebuild):