ParseWithOptions: add the ability to override defaultTypeParsers #272
+23
−1
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.
This small fix/feature adds the ability to override default ParserFunc in Options{FuncMap} for ParseWithOptions
When it can be useful:
When for some reason you can't use default ParseDuration format but want to have a time.Duration
Like today I ran into a small but very annoying problem
I had some executions like
INTERVAL=1 ./script.sh
and wanted to override time.Duration parser but it was not possible.We may also want to override the URL parser or some other future defaultTypeParsers