[pluginApi] expose support flags #5941
Closed
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
With elastic#5871 we removed support for configuration-based autoloading and moved to require-based autoloading. This change is difficult for plugin authors to make in a backwards compatible way so I thought it would make sense to start helping plugin authors know which features are/are not available to them with a simple collection of "supports" flags. For now it just shows that `autoload: false`, so that plugins can expose an alternate main file which includes the autoloads they require
|
From IRC:
|
|
Meh, I agree, this is gross |
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.
With #5871 we removed support for configuration-based autoloading and moved to require-based autoloading. This change is difficult for plugin authors to transition through in a backwards compatible way so I thought it would make sense to start helping plugin authors know which features are/are not available to them with a simple collection of "supports" flags. For now it just shows that
autoload: false, so that plugins can expose an alternate main file which includes the autoloads they require.