Skip to content

Conversation

theEvilReaper
Copy link
Contributor

Proposed changes

We can enforce NotNull annotation by default using the package-info file. This way, all elements are considered non-null unless explicitly annotated as nullable. It improves readability by reducing redundant annotations and highlighting only the cases where null is actually allowed.

Types of changes

What types of changes does your code introduce to this project?
Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.

  • I have read the CONTRIBUTING.md
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

@theEvilReaper theEvilReaper merged commit 8cc68f9 into develop Sep 12, 2025
7 checks passed
@theEvilReaper theEvilReaper deleted the feature/packageInfo branch September 12, 2025 19:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants