-
Notifications
You must be signed in to change notification settings - Fork 17.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
time: quote original text in error returned by ParseDuration #38295
Comments
I see that |
hi, I would like to help, can i work on this? |
@obeyda Thanks for offering. In this case it seems like @bruce-ricard is already planning to send in a change, according to the initial bug submission. |
@obeyda if you want to help and work on it, go ahead. I can help you by reviewing your change if you want to. Let me know. |
@bruce-ricard sure thing, I'll start working on this and submit a CL. |
Change https://golang.org/cl/227878 mentions this issue: |
time.ParseDuration now quotes the original value provided to the function. This change modifies the assertion to handle the quotes when present. See golang/go#38295 Signed-off-by: Matthew Sykes <[email protected]>
time.ParseDuration now quotes the original value provided to the function. This change modifies the assertion to handle the quotes when present. See golang/go#38295 Signed-off-by: Matthew Sykes <[email protected]>
added wrapper for external errors, come outside the module to detect them in tests despite its content (golang/go#38295)
I am trying to parse some time strings using the standard library. I am trying to parse the time "for breakfast" (literally).
What did you expect to see?
I would expect to see an error message explaining clearly what I did wrong.
What did you see instead?
That's not very helpful.
would be highly more useful for debugging.
Please think of using quotation marks for quoted text when writing natural language like English.
This part of the code in particular, contains quite a few occurrences of quoted text without quotation marks.
I am happy to submit a PR if you agree this is a good change.
The text was updated successfully, but these errors were encountered: