Skip to content

Use to JSpecify for nullness checks #3159

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

Open
wants to merge 9 commits into
base: main
Choose a base branch
from
Open

Use to JSpecify for nullness checks #3159

wants to merge 9 commits into from

Conversation

christophstrobl
Copy link
Member

Closes: #3092

@christophstrobl christophstrobl changed the title Move to jpsecify for nullness checks. Move to jspecify for nullness checks. May 28, 2025
@mp911de mp911de changed the title Move to jspecify for nullness checks. Use to JSpecify for nullness checks Jul 1, 2025
@mp911de mp911de added the type: enhancement A general enhancement label Jul 1, 2025
@mp911de mp911de marked this pull request as ready for review July 1, 2025 11:46
mp911de added 2 commits July 1, 2025 15:33
JUnit 5.13 introduced some changes to their API and therefore, we need to stay on the older version until migrating to parametrized test classes.

See #3167
Add missing package info, fix invalid nullness annotations, reduce nullability.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement A general enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Migrate to JSpecify annotations for nullability constraints
2 participants