Skip to content

Conversation

@weberhofer
Copy link

Pull Request

Description

This PR adds support for the JSpecify annotations: @NullMarked, @NullUnmarked, @nullable, @nonnull

Fixes: #4848

Type of Change

  • πŸ› Bug fix
  • ✨ New feature
  • ♻️ Refactor (non-breaking change)
  • πŸ§ͺ Tests
  • πŸ“ Documentation
  • 🧹 Chore (build or tooling)

Checklist

  • I have added/updated tests as needed
  • I have added/updated documentation where applicable
  • The PR title is descriptive
  • The code builds and passes tests locally
  • I have linked related issues (if any)

Comment on lines 1 to 4
@NullUnmarked
package io.swagger.v3.jaxrs2.resources.jspecify.nullunmarked;

import org.jspecify.annotations.NullUnmarked; No newline at end of file
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From my understanding of JSpecify, @NullUnmarked is only relevant within a @NullMarked package, so you could move this package to ...jspecify.nullmarked.nullunmarked

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for reviewing. I have updated the PR.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're welcome.

Unfortunately that's all I can do as I'm not on the team.

Another suggestion is that you might be better to rebase your commits onto main and force push, instead of merging it in. Typically maintainers prefer PRs without merge commits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ModelResolver#resolve ignores TYPE_USE annotations on property types

2 participants