tactics: exposing ext_options/all_ext_options #3034
Merged
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.
cc @nikswamy, there's no way to access them from tactics otherwise as of yet, right?
Also I wonder if it would be more future proof to provide a KV interface, such as:
And writing
--ext k=v
to define one. The key could use dots to separate namespaces purely as a convention. We could maybe define anext_options
analogue that looks at the prefix of each key to decide which pairs to return.