Throw constant values when recovering and map those constants to localized error messages.
Categories
(Firefox :: Profile Backup, task, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox130 | --- | fixed |
People
(Reporter: fchasen, Assigned: sthompson)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fidefe-device-migration])
Attachments
(1 file)
We should convert the exceptions that are throw during the recoverFromBackupArchive process to throw constant values inside of the cause property of the errors. Those constants should be in ArchiveUtils if possible.
Will also need to map the constants to the right localized error message string to display in Bug 1905154 or a generic error message string.
Updated•1 year ago
|
Comment 1•1 year ago
|
||
Those constants should be in ArchiveUtils if possible.
I thought about it a bit more, and considering that we might want those constants to be available inside some of our UI components, we might want to create a new non .sys module that just contains constants. BackupConstants.mjs or something.
Comment 2•1 year ago
|
||
Bug 1904949 added a bunch of cause values for exceptions thrown in BackupService, so that part is done. This bug is about making sure those constants get mapped to friendly error messages to users.
Updated•1 year ago
|
| Assignee | ||
Comment 3•1 year ago
|
||
Updated•1 year ago
|
Comment 6•1 year ago
|
||
| Assignee | ||
Comment 7•1 year ago
|
||
I was explicitly packaging a single JS file using both moz.build and jar.mn in order to use the file from different contexts. I did not know that this type of duplication was discouraged.
I am working on an alternative solution to packaging the single JS file once.
Comment 9•1 year ago
|
||
| bugherder | ||
Description
•