Configure parser extensions via CLI argument#331
Open
cr3bs wants to merge 5 commits into
Open
Conversation
cr3bs
force-pushed
the
feat/parser-extensions-cli-arg
branch
from
ec07419 to
a4d5957
Compare
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
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.
Hey there,
first of all thank you for the whole cooklang ecosystem! I really like the idea and want to contribute something.
Most of the recipes that I have, need at least some of the extensions. As there is currently no way to configure these (although supported by the parser), I have created this PR.
Enabling all extensions, as done in #210 (no offence, tried this myself :) ), does work but might have side effects which are not desired. This PR allows to configure them globally, so users are free to choose whatever extensions they like. The default behaviour is not modified.
Fixes #219
Cheers!