redhat-developer / redhat-developer/quarkus-ls
Relaxed plugin validation and errors (false positive)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 50
- Forks
- 18
- Avg merge
- 22h 11m
- Merged PRs (30d)
- 3
Description
I do believe that it is essential for the Quarkus plugin to be relaxed about raising errors when they are not 100% sure (totally avoiding false positive).
The plugin is here as a helper to make things easier and quicker, the validation is a nice to have (and should be best effort). When there is the question of raising an error, the plugin should:
- if this is a guaranteed error, raise it
- if this is a possible error or missing value, show a very light warning
Anyway Quarkus build is here as backup to make sure everything is fine for the user.
This is a false positive:
This is a good weak warning:
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
The issue does not name a file, test, or entry point. Start by reproducing the shown false-positive validation and tracing the plugin's error and warning reporting paths; done means guaranteed errors still raise errors while possible errors or missing values produce only light warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100