You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This isn't necessarily an issue, more a feature request, but it might be nice to have better error handling for when requests fail or otherwise don't behave as expected. In the previous issue I made, #209, I was unable to favorite the show I was researching because of a partial API failure. With proper data validation though, the page could still be allowed to open so that the description can be viewed, favorites made, etc. As is, I am unable to do either of those things because of the episode error. Instead, this error could be relegated elsewhere, like an in-app notification/banner, or even just in the episodes section itself for a quick and dirty fix. I whipped up a quick demo showing that latter option just to show how it looks in-app:
Acknowledgements
I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
The text was updated successfully, but these errors were encountered:
Extension information
All
Steps to reproduce
N/A
Miru version
1.8.1
Other details
This isn't necessarily an issue, more a feature request, but it might be nice to have better error handling for when requests fail or otherwise don't behave as expected. In the previous issue I made, #209, I was unable to favorite the show I was researching because of a partial API failure. With proper data validation though, the page could still be allowed to open so that the description can be viewed, favorites made, etc. As is, I am unable to do either of those things because of the episode error. Instead, this error could be relegated elsewhere, like an in-app notification/banner, or even just in the episodes section itself for a quick and dirty fix. I whipped up a quick demo showing that latter option just to show how it looks in-app:
Acknowledgements
The text was updated successfully, but these errors were encountered: