spring-projects / spring-projects/spring-tools
[jspecify] ask user to enable null analysis after project import
Open
Nobody has claimed this yet.
for: eclipse
type: enhancement
- Dominant language
- Java
- Stars
- 983
- Forks
- 240
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 7
Description
Similar to the Java tooling in VSCode, we should ask users to automatically enable annotation based null analysis for their projects on project import in case the project contains JSpecify on the classpath.
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 by locating the existing Java tooling behavior in VS Code for enabling annotation-based null analysis during project import. Then trace project-import handling and JSpecify classpath detection; done means an imported project containing JSpecify prompts the user to enable null analysis, with behavior verified against the comparable Java tooling flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, vscode
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100