Skip to content

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.
@mp911de mp911de added this to the 4.0 M4 (2025.1.0) milestone Jul 3, 2025
mp911de pushed a commit that referenced this pull request Jul 3, 2025
Closes #3092
Original pull request: #3159
mp911de added a commit that referenced this pull request Jul 3, 2025
Add missing package info, fix invalid nullness annotations, reduce nullability.

Add missing nullability annotations. Reformat code. Refine nullability flows and warnings.

See #3092
Original pull request: #3159
@mp911de
Copy link
Member

mp911de commented Jul 3, 2025

Thank you for your contribution. That's merged and polished now.

@mp911de mp911de closed this Jul 3, 2025
@mp911de mp911de deleted the issue/3092 branch July 3, 2025 13:40
@mp911de mp911de self-assigned this Jul 3, 2025
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

3 participants