fix(ui): moment deprecated date formatting in getFormattedTimestamp()
#102599
Conversation
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
This fixes the following console.warn that we are getting in prod: ``` Deprecation warning: value provided is not in a recognized RFC2822 or ISO format. moment construction falls back to js Date(), which is not reliable across all browsers and versions. Non RFC2822/ISO date formats are discouraged. Please refer to http://momentjs.com/guides/#/warnings/js-date/ for more info. Arguments: ``` `getRelativeTime()` is passed 2 `moment` objects that are formatted into a non-standard date string, that is used to re-create another `moment` object. We can use the `moment` arguments directly instead.
github-actions
bot
added
the
Scope: Frontend
Member
Author
|
@sentry review |
scttcper
approved these changes
Nov 3, 2025
billyvg
deleted the
billy/fix-moment-deprecation-warning-getRelativeTime
branch
shashjar
pushed a commit
that referenced
this pull request
Nov 4, 2025
…)` (#102599) This fixes the following console.warn that we are getting in prod: ``` Deprecation warning: value provided is not in a recognized RFC2822 or ISO format. moment construction falls back to js Date(), which is not reliable across all browsers and versions. Non RFC2822/ISO date formats are discouraged. Please refer to http://momentjs.com/guides/#/warnings/js-date/ for more info. Arguments: ``` `getRelativeTime()` is passed 2 `moment` objects that are formatted into a non-standard date string, that is used to re-create another `moment` object. We can use the `moment` arguments directly instead.
priscilawebdev
pushed a commit
that referenced
this pull request
Nov 6, 2025
…)` (#102599) This fixes the following console.warn that we are getting in prod: ``` Deprecation warning: value provided is not in a recognized RFC2822 or ISO format. moment construction falls back to js Date(), which is not reliable across all browsers and versions. Non RFC2822/ISO date formats are discouraged. Please refer to http://momentjs.com/guides/#/warnings/js-date/ for more info. Arguments: ``` `getRelativeTime()` is passed 2 `moment` objects that are formatted into a non-standard date string, that is used to re-create another `moment` object. We can use the `moment` arguments directly instead.
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.
This fixes the following console.warn that we are getting in prod:
getRelativeTime()is passed 2momentobjects that are formatted into a non-standard date string, that is used to re-create anothermomentobject. We can use themomentarguments directly instead.