Fix for Jest tests both not running and not passing #83
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add explicit dev dependency on `ts-node`, which fixes an configuration
issue with TypeScript/`ts-jest` that would prevent tests from running.
- Update the DateTime JSON conversion tests:
- Update the deserializer logic so that it applies the zone offset to the
resulting DateTime object if there is one in the ISO String
- Use the ISO strings for equality comparisons, since the `.equals()` method
on the DateTime object does a field-wise deep comparison, and zones don't
serialize/deserialize symmetrically.
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes
ts-node, which fixes a configuration issue with TypeScript/ts-jestthat would prevent tests from running..equals()method on the DateTime object does a field-wise deep comparison, and zones don't serialize/deserialize symmetrically.