Change registerPlugin to add plugin after Extensions plugins #658
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 commit changes
registerPlugin
by 1. adding the new plugin tothis.plugins
and 2. updatingthis.plugins
withinthis.state.plugins
by splicing with the newthis.plugins
length. Previously, new plugins were simply added to the end ofthis.state.plugins
and were not appended tothis.plugins
.By placing registered plugins at this new location within
this.state.plugins
, we prioritize registered plugins over default ProseMirror plugins such askeymap(baseKeymap)
. This will allow new plugins to have precedence over props such ashandleKeyDown
. A use case of this defining a floating Editor Menu that's navigable with arrow and enter keys.