feat(gherkin): added custom flavor registry #95
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's changed?
Added the ability to register custom token matcher for custom "gherkin flavors".
"generateMessages" and "makeSourceEnvelopes" will try to match the file extension / media type with the according custom flavor and use the appropriate matcher.
⚡️ What's your motivation?
I would like to implement a custom "flavor" using asciidoc much like the one with markdown that already exists in the repository.
Also implementing such feature adds an SPI-like capabilities for everyone to implement whatever they like as "flavors" and keeps the open / close principle.
related to #10
🏷️ What kind of change is this?
♻️ Anything particular you want feedback on?
📋 Checklist:
This text was originally generated from a template, then edited by hand. You can modify the template here.