Skip to content
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

Separate "plugin" exceptions from ApeExceptions and show stack-traces #2214

Open
antazoey opened this issue Aug 9, 2024 · 1 comment
Open
Labels
0.9 category: feature New feature or request

Comments

@antazoey
Copy link
Member

antazoey commented Aug 9, 2024

Overview

This is a 0.9 TODO I am adding right now.
Issue: ApeException is mis-used in certain spots, such as raising exceptions when things go wrong that are not really the project-developer's fault (but likely ours or the Plugin developers fault). In this case, we should be more verbose by default and include pretty stacktraces and what-not instead of treating it as a user-hour where the info is too verbose.

Specification

New base ApePluginException and in the global Ape err handler, except: that one before ApeException and don't omit anything, maybe raise or rich.print(stacktrace) or something.

Maybe an aside or separate issue:
I would like to delete ape test --show-internal and only use the logger... verbose loggers are supposed to show internal anyway, and we already changed the default verbosity for ape test

Dependencies

Include links to any open issues that must be resolved before this feature can be implemented.

@antazoey antazoey added category: feature New feature or request 0.9 labels Aug 9, 2024
Copy link

linear bot commented Aug 9, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.9 category: feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant