Values from flags should override values in prompt yaml files. #49
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?
Very small follow up from #48:
Why?
Suppose I have a template in a prompt.yaml that defines model parameters (or even model name). If I want to iterate on the temperature, or even which model i want to use then it's easier to do so by repeatedly running the cmd and tweaking the flag value.
Basically, a cli flag has a higher order of "specificity" than the value in the yaml file. I'm more intentional, it is surprising that the cli flag value might be silently ignored.
Bonus observation
About 80% of this test was written via the following prompt: