[refactor] Better integrate new internal plugins #108
Merged
Conversation
This file contains 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
…on + uniformisation
yoannmoinet
changed the title
yoannmoinet
force-pushed
the
yoann/new-internal-plugins
branch
2 times, most recently
from
9757247
to
82ed7f6
Compare
yoannmoinet
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What and why?
Now that we consider internal plugins almost the same as external plugins,
we need to better integrate how we create and verify them.
How?
yarn cli create-plugin.yarn cli integrity.Note
I will remove
Check integrity of our filesfrom the expected checks once this PR is merged.