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.
The error occurred because some ticks had malformed dates that couldn't be parsed into valid Date objects, causing the getTime() function to fail. This change gracefully handles those cases while maintaining the intended noon UTC standardization.
This change:
Handles both Date objects and string dates (references test data in src/model/tests/ticks.ts lines 19 and 31)
Validates dates properly before using getTime() (fixes the error in the GraphQL response)
Sets invalid dates to null instead of throwing errors (maintains data consistency)
Maintains compatibility with the America/Denver timezone standardization from the migration (references db-migrations/0003-date-climbed-to-date.js)
Matches the test expectations for date handling (references src/tests/ticks.ts line 193)
I also added a test. screenshots on repro of error, successful testing after change and successful running test
After Change