API Catalog does not serve error stack trace in case of exception
Open
Nobody has claimed this yet.
bug
Priority: Low
size/M
- Dominant language
- Java
- Stars
- 92
- Forks
- 81
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 46
Description
Describe the bug
API Catalog does not display any stack in case of an error.
Steps to Reproduce
- simulate an error (ie. change value inside developer console to null or change the source code)
- BigShield appears a should contain but without any stack in there
Expected behavior
There should be a stack of the error
Screenshots
Logs
If applicable, add server logs collected at the time of your problem.
Details
- Version and build number: 3.5.0-RC1 (and probably previous versions)
- Test environment: localmachine
API Catalog Web UI (in case of API Catalog issue):
- OS: Windows
- Browser: Chrome
- Version: the latest one
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the API Catalog Web UI error path and reproduce the exception described in the issue by changing a value to null or altering the source. Trace how the error is rendered in Chrome, then verify that the displayed error includes its stack trace.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100