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
Most of the 7.9 Errors I've found so far in basic features are just Business Rules exceptions. They aren't even that bad. However, if an end user sees them out of nowhere, they seem more severe and scary than they actually are.
A very possible and emotionally heartbreaking side effect these Business Rules exceptions could cause is that end users will start saying 7.9 is more buggy than previous versions when in reality it's relatively one of our most tested and worked on versions.
For example, this error below does not deserve to have an error message this large and intimidating.
The text was updated successfully, but these errors were encountered:
In production instances, the error messages are formatted correctly.
In development instances, Django should be supplying html to the frontend, which can then render it appropriately.
The problem is this has stopped working somewhere down the line, and the frontend is instead rendering/accepting it as plain text rather than html.
Most of the 7.9 Errors I've found so far in basic features are just Business Rules exceptions. They aren't even that bad. However, if an end user sees them out of nowhere, they seem more severe and scary than they actually are.
A very possible and emotionally heartbreaking side effect these Business Rules exceptions could cause is that end users will start saying 7.9 is more buggy than previous versions when in reality it's relatively one of our most tested and worked on versions.
For example, this error below does not deserve to have an error message this large and intimidating.
The text was updated successfully, but these errors were encountered: