Bugs related to trying to adopt vertx-shell in a mature Vertx project
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 39
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
- Installing its own body handler, when one might be already specified on the route, is kind of a drag
- I got the pages to render, but then the SockJS call would fail.
- Implementing AuthOptions is fine, but a tedious surprise
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
No files or tests are named. Start by locating the vertx-shell route and request-handling entry points, then investigate the existing body handler, failing SockJS call, and AuthOptions behavior described in the issue; done means each adoption problem has a confirmed resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100