Add higher priority on generating element regex#143
Merged
essamamdani merged 1 commit intoEnclavely:masterfrom Nov 21, 2017
Merged
Add higher priority on generating element regex#143essamamdani merged 1 commit intoEnclavely:masterfrom
essamamdani merged 1 commit intoEnclavely:masterfrom
Conversation
…nts are successfully registered by increasing the action priority
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently, we add an action to generate element regex at default priority
10means it's possible to occur before custom elements are registered.By putting higher priority e.g
999it will make sure that generate regex action will be fired at the very end oftailor_register_elementshook.