Skip to content

Migrate to JSpecify Annotations for nullability constraints #1132

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.

Sign up for GitHub

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

Jump to bottom
Closed
rstoyanchev opened this issue Feb 19, 2025 · 0 comments
Closed

Migrate to JSpecify Annotations for nullability constraints #1132

rstoyanchev opened this issue Feb 19, 2025 · 0 comments
Assignees
@bclozel
Labels
type: enhancement A general enhancement
Milestone
2.0.0-M1

Comments

@rstoyanchev
Copy link
Contributor

Following on the migration in Spring Framework spring-projects/spring-framework#28797, we will also migrate in Spring for GraphQL.
@rstoyanchev rstoyanchev added the type: enhancement A general enhancement label Feb 19, 2025
@rstoyanchev rstoyanchev added this to the 2.0.x milestone Feb 19, 2025
@bclozel bclozel self-assigned this Apr 18, 2025
@bclozel bclozel modified the milestones: 2.0.x, 2.0.0-M1 May 16, 2025
bclozel added a commit that referenced this issue May 21, 2025
@bclozel
Suppress AnnotationLocation checkstyle rule
7131a15 
This rule flags valid usages because it conflates annotated methods and
annotated return types, considering that the `@Nullable` annotation
should be on its own line. For example, the following fails:

```
@OverRide
@nullable String getName() {
```

See gh-1132
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bclozel bclozel

Labels
type: enhancement A general enhancement
Projects
None yet
Milestone
2.0.0-M1
Development

No branches or pull requests
2 participants
@bclozel @rstoyanchev