Change Details

Now that {T315481} is merged, any errors that occur within Phonos will break parsing/saving of the entire page. We should catch the ones we know are unrecoverable (those all //should// be `PhonosException`s, and if they're not, we need to add them). For now the output can simply be what the error message is, except localized which we haven't implemented yet. !! //To be filled in for QA purposes: list all the "known" kinds of error that we might encounter// !! **Acceptance criteria** * All known fatal exceptions should be captured, with localized messages displayed to the user * Designs can be ironed out in a separate task as needed. The important part is nothing interrupts parsing/saving of the page.

Now that {T315481} is merged, any errors that occur within Phonos will break parsing/saving of the entire page. We should catch the ones we know are unrecoverable (those all //should// be `PhonosException`s, and if they're not, we need to add them). For now the output can simply be what the error message is, except localized which we haven't implemented yet. !! //To be filled in for QA purposes: list all the "known" kinds of error that we might encounter// !! **Acceptance criteria** * All known fatal exceptions should be captured, with localized messages displayed to the user * Designs can be ironed out in a separate task as needed. The important part is nothing interrupts parsing/saving of the page. * Recoverable errors such as a missing file should not prevent Phonos from outputting the button as usual (as we have user-friendly error messages for that)

Now that {T315481} is merged, any errors that occur within Phonos will break parsing/saving of the entire page. We should catch the ones we know are unrecoverable (those all //should// be `PhonosException`s, and if they're not, we need to add them). For now the output can simply be what the error message is, except localized which we haven't implemented yet. !! //To be filled in for QA purposes: list all the "known" kinds of error that we might encounter// !! **Acceptance criteria** * All known fatal exceptions should be captured, with localized messages displayed to the user * Designs can be ironed out in a separate task as needed. The important part is nothing interrupts parsing/saving of the page. * Recoverable errors such as a missing file should not prevent Phonos from outputting the button as usual (as we have user-friendly error messages for that)