Resolve plugin definitions from registry #141
Merged
Conversation
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
bentsherman
force-pushed
the
plugin-index-file
branch
from
79b3932 to
68d6335
Compare
Closed
bentsherman
force-pushed
the
plugin-index-file
branch
from
9cd8303 to
4f3848a
Compare
bentsherman
changed the title
bentsherman
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 PR uses the plugin registry to load config scopes for third-party plugins.
It looks at the
pluginsblock in a given config file to determine which plugin definitions to fetch. If a version is not specified, the latest version is used by default.A future iteration should use the plugin definitions fetched by the config parser to recognize custom functions / factories / operators in the script.
TODO: