parser/formatter plugin helper with default @type in plugin side #1267
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.
Adding
multi: true
forconfig_section :parse
andconfig_section :format
helps plugin authors not to useconf
ordefault_type
argument inparser_create
andformatter_create
.With this change, plugin authors can write code to create parser(formatter) instances with default parser(formatter).
After this change, parser(formatter) plugin helpers always requires default
@type
definition.I believe that it's reasonable change for all plugins which uses parsers/formatters.