Use JSpecify’s annotations to document nullability

Open
#2,024 5 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
java, kotlin
Domain
developer-experience

Research direction

The issue names no files, tests, or entry points. Start by locating the SDK's public model declarations and checking how Kotlin currently infers their nullability; done means the relevant API surface uses JSpecify annotations and Kotlin consumers receive useful nullability information.

Written by the indexing model from the issue text.

Description

feature-request future

I use Stripe SDK with Kotlin. It would be beneficial to have nullability information.

Dominant language
Java
Stars
1k
Forks
406
Avg merge
2d 18h
Merged PRs (30d)
20

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stripe/stripe-java

All issues in stripe/stripe-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.