-
Notifications
You must be signed in to change notification settings - Fork 5
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
Extend a problem by stacktrace, too. #38
Comments
Thx. This should definitely be made configurable. Personally, I don't want to present internal exceptions to the user. But there may be other use cases. Or like you have implemented as a "devmode" feature. |
@CrystalMethod You mentioned https://github.com/SchulteMarkus/quarkus-problem-extension/commit/251a8cb67b84825e5504de978cd67aef97a11bf4 cannot be used for time being, as because of native image there has additional work to be done. I think 251a8c would be a good start. What additional work has to be done? |
I had a closer look at your solution for stacktraces. Without having actually tried it in native mode, I can imagine that this solution also works in native mode. I was referring to the use of the solution described here to publish stacktraces. Zalando is using SPI/Service Loader and this wan't work in native mode out of the box. |
Ah I see. |
Zalando problem supports stacktraces as part of an API "problem" response, see https://github.com/zalando/problem#stack-traces-and-causal-chains
Feature request
This extension provides stacktraces, too
Additional context
The text was updated successfully, but these errors were encountered: