fix(nlp): parse day after tomorrow distinctly#940
Open
DhruvalBhinsara1 wants to merge 2 commits into
Open
Conversation
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Fixes a bug in matchRelativeDay where the "tomorrow" regex would match before the more specific "day after tomorrow" pattern, causing the latter to be misclassified as "tomorrow". Adds a Node test that validates both phrases resolve to the correct dates.
Changes:
- Reordered regex checks in
matchRelativeDayso "day after tomorrow" is matched before "tomorrow". - Added a new Node-based test that loads the ESM module via a data URL and asserts both relative-day cases.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| js/utils/nlpDateExtractor.js | Reorders relative-day matching so the more specific "day after tomorrow" pattern is checked first. |
| tests/nlpDateExtractor.test.js | New test exercising both "tomorrow" and "day after tomorrow" inputs using a fixed now. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or 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
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.
What
Fixes the frontend NLP fallback so
day after tomorrowresolves two days ahead instead of being swallowed by the shortertomorrowmatch. This keeps the browser fallback behavior aligned with the server fallback and closes #939.How
Moved the
day after tomorrowcheck before the generictomorrowregex injs/utils/nlpDateExtractor.js. Added a focused Node regression test that imports the browser ESM helper through afile://URL, pins the timezone to UTC for deterministic date assertions, and verifiestomorrowandday after tomorrowresolve to distinct dates.Testing
npm testnpx -y node@20 --testgit diff --checknode --input-type=module --check < js/utils/nlpDateExtractor.jsRisks / Notes
No UI change, so screenshots are not applicable.
npm cicompleted successfully and reported existing moderate audit findings; no dependencies were changed.Related Issue
Closes #939
Summary
Corrects relative-day parsing in the frontend fallback extractor.
Changes Made
day after tomorrowbefore the shortertomorrowpattern.Screenshots
N/A - parser logic only.
Checklist