Allow passing custom editor creator to slate-hyperscript createEditor
#4555
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.
Description
Just like in slate's core, I use
slate-hyperscript
to perform tests for my particular editor. This change makes it easier to create your own testing setup by allowing you to pass your own slateEditor
instance toslate-hyperscript
'screateEditor
. This way you can simply reuse the setup code that's in there without needing to duplicate that code in your own setup.Issue
Fixes: (link to issue)
Example
createHyperscript
would then look like thiscreateEditor
then takes care of setting theanchor
andfocus
properly given the JSX.Checks
yarn test
.yarn lint
. (Fix errors withyarn fix
.)yarn start
.)yarn changeset add
.)