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
We need to establish a policy on messaging, and we're thinking about establishing that policy based on error level. If makes sense to me to present all messages with an error level of major and up, and write all other lesser errors to a .txt output file.
This approach does not currently appear to reflect messages with good news. @HenryGeorgist is there a way that we can incorporate good news messages (e.g. compute finished!) into a general policy about what level of messaging to display to the user vs to only write to text file?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
We need to establish a policy on messaging, and we're thinking about establishing that policy based on error level. If makes sense to me to present all messages with an error level of major and up, and write all other lesser errors to a .txt output file.
The error levels are here: https://github.com/HydrologicEngineeringCenter/Framework/blob/master/Base/Enumerations/ErrorLevel.cs
This approach does not currently appear to reflect messages with good news. @HenryGeorgist is there a way that we can incorporate good news messages (e.g. compute finished!) into a general policy about what level of messaging to display to the user vs to only write to text file?
Beta Was this translation helpful? Give feedback.
All reactions