docs: document parse behavior with non-format strings #38
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.
I came across this behavior while using ptera to parse ISO strings without milliseconds. It's clear from the tests that this is the intended behavior, but I didn't notice this documented anywhere, so this PR updates the docs to cover the behavior of
parse
when non-format strings are in play.Alternatively, the parse function could be updated to only handle format strings. A test to confirm the behavior can be added by applying this diff