Skip to content

Conversation

@therepanic
Copy link
Contributor

Required for automatic validation and detection of classes that violate null validation rules.

Refers to this comment: #302 (comment)

@therepanic
Copy link
Contributor Author

Hello, @onobc. I see you recently worked on replacing @Nullable imports with identical JSpecify ones.

You need to add package-info to each package to fully utilize JSpecify. However, in your commit, you did not additionally mark @Nullable where necessary.

Because of this, the current build crashes. I can polish this in a separate commit and specify the annotation where necessary, or if you want to do it, you can use my commit as a basis.

@onobc
Copy link
Contributor

onobc commented Nov 25, 2025

Hi @therepanic , yeh I was just getting started on this now. I will take these package infos in your commit and use them in my PR (I have them locally but have not added the javadoc comment to each but you have 😄 ). I'll take it from here.

Thank you! It is so cool to have community members (in this case - you and @lobaorn-bitso) always having my back.

@onobc
Copy link
Contributor

onobc commented Nov 25, 2025

Closing in favor of #304

@onobc onobc closed this Nov 25, 2025
@onobc onobc reopened this Nov 25, 2025
@onobc onobc closed this Nov 25, 2025
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.

2 participants