Parse and reformat datetimes only when defined via value-class pattern #89
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 change updates four tests dealing with datetime attributes. The MF2 spec (as of July 2018) specifies that datetime attributes should be parsed and reformatted only when they are defined in the original document via value-class pattern. In every other instance, they are to be treated as literal strings, and passed through to the resulting JSON file unchanged.
The updates here deal specifically with datetimes not defined via value-class pattern, and which therefore should have JSON representations that match their appearance in their respective source HTML files.