Closed
Bug 1953204
Opened 1 year ago
Closed 1 year ago
Reword JSMSG_TEMPORAL_PLAIN_MONTH_DAY_INVALID error message.
Categories
(Core :: JavaScript: Standard Library, enhancement, P3)
Core
JavaScript: Standard Library
Tracking
()
RESOLVED
FIXED
139 Branch
| Tracking | Status | |
|---|---|---|
| firefox139 | --- | fixed |
People
(Reporter: dminor, Assigned: tannal2409, Mentored)
References
(Blocks 1 open bug)
Details
(Keywords: good-first-bug)
Attachments
(1 file)
The JSMSG_TEMPORAL_PLAIN_MONTH_DAY_INVALID is used to report invalid month and day fields to the user.
The current wording is "year-month-day must be valid iso dates", I think it would be more helpful to say "month-day must be valid ISO date values".
This is a good first bug, the main complexity will be getting the SpiderMonkey / Firefox build working.
- Make sure you can build SpiderMonkey. You can find instructions on building here: https://firefox-source-docs.mozilla.org/js/build.html.
- Change the error message, and then make sure the build is still working and you can run the tests. You might need to make some changes to the tests if they were expecting the old error message.
- Now you can commit your changes. Your commit message should look like:
Bug X - Reword JSMSG_TEMPORAL_PLAIN_MONTH_DAY_INVALID error message; r=dminor!, where X is the number for this bug. - Once you have your changes committed, request review. There are instructions on using phabricator and on getting reviews.
Updated•1 year ago
|
Severity: -- → N/A
Priority: -- → P3
| Assignee | ||
Comment 1•1 year ago
|
||
Updated•1 year ago
|
Assignee: nobody → tannal2409
Status: NEW → ASSIGNED
Pushed by dminor@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/3e4242a6e73f
Reword JSMSG_TEMPORAL_PLAIN_MONTH_DAY_INVALID error message. r=dminor
Comment 3•1 year ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox139:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 139 Branch
Updated•1 year ago
|
QA Whiteboard: [qa-triage-done-c140/b139]
You need to log in
before you can comment on or make changes to this bug.
Description
•