-
Notifications
You must be signed in to change notification settings - Fork 881
Implement a standard way to handle errors on the ui/cli #764
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@f0ssel are you still picking up this one? just checking in because there's not any implementation details. lmk if you need any support or if you think someone else should pick it up. |
Please add your planning poker estimate with ZenHub @f0ssel |
Please check with @presleyp about the frontend handler for errors in V2. Changes to how we handle errors may have an impact on that work. |
Please add your planning poker estimate with ZenHub @presleyp |
I think the action item here is just a discussion on how we'd like to do this generically between the BE and FE. I'll setup something with @presleyp and we can chat. |
@f0ssel Did you get a chance to set up the convo mentioned above? |
As a developer, I want a consistent was to handle errors in the UI and CLI.
The text was updated successfully, but these errors were encountered: