Should --get throw a warning if a variable is unknown #236
Closed
jacobmealey
started this conversation in
Ideas
Replies: 2 comments 1 reply
-
A third option is to error out completely, to make it more apparent if you spelled a keyword wrong etc... I have a feeling we are not going to add many more keywords going forward so there is little risk that you're going to end up in a situation where you run an older version using a newer command line and thus using a keyword not yet implemented. |
Beta Was this translation helpful? Give feedback.
1 reply
-
See #286 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
currently if you call
trurl --url "https://example/com" -g "{host} {foo}"
it will printexample
. I think it should either printexample {foo}
orexample
to stdout and some type of warning to stderr that says "Unkown variable foo". I'm leaning towards the warning to stderr and usingtrurl_warnf
like in #231.Beta Was this translation helpful? Give feedback.
All reactions