Thanks to visit codestin.com
Credit goes to github.com

Skip to content

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

Closed
Tracked by #1479
misskniss opened this issue Mar 31, 2022 · 6 comments
Closed
Tracked by #1479

Implement a standard way to handle errors on the ui/cli #764

misskniss opened this issue Mar 31, 2022 · 6 comments
Labels
api Area: HTTP API

Comments

@misskniss
Copy link

As a developer, I want a consistent was to handle errors in the UI and CLI.

@misskniss misskniss added this to the V2 Beta milestone Mar 31, 2022
@tjcran
Copy link

tjcran commented Apr 22, 2022

@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.

@misskniss
Copy link
Author

Please add your planning poker estimate with ZenHub @f0ssel

@misskniss
Copy link
Author

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.

@misskniss
Copy link
Author

Please add your planning poker estimate with ZenHub @presleyp

@f0ssel
Copy link
Contributor

f0ssel commented Apr 28, 2022

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.

@misskniss
Copy link
Author

@f0ssel Did you get a chance to set up the convo mentioned above?

@f0ssel f0ssel closed this as not planned Won't fix, can't repro, duplicate, stale Jul 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Area: HTTP API
Projects
None yet
Development

No branches or pull requests

5 participants