Add error handling for alt text API #330
Merged
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.
Does this PR close any open issues?
Closes #324
Give a longer description of what this PR addresses and why it's needed
This PR adds error handling for aggregated plots which we can't generate alttxts for. Previously, Upset would silently refuse to update an alttxt for an aggregated plot without informing the user. Now, an error message is displayed when attempting to generate an alttxt for an aggregated plot. Additionally, more error handling was added for errors from the alttxt API; appropriate error messages are displayed if the API fails with a 400 code, 500 code, or other code. Finally, a test was added to Playwright to ensure that the error message displays for aggregated alttxt generation.
Provide pictures/videos of the behavior before and after these changes (optional)
Before:


After:
Have you added or updated relevant tests?
Have you added or updated relevant documentation?
Are there any additional TODOs before this PR is ready to go?
TODOs: