Skip to content
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.

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

Clarify @Nullable and @Nonnull usage [ci skip] #6095

Merged

Conversation

optionsome
Copy link
Member

Summary

Trying to clarify which annotations should be used in code.

Issue

No issue as minor code conventions clarification.

Unit tests

No

Documentation

Touched documentation

Changelog

No need

@optionsome
Copy link
Member Author

I wasn't completely sure what is our stance on these so we can discuss this quickly in a developer meeting next week.

@leonardehrenfried leonardehrenfried changed the title Clarify @Nullable and @Nonnull usage Clarify @Nullable and @Nonnull usage [ci skip] Sep 27, 2024
@t2gran t2gran added this to the 2.7 (next release) milestone Oct 8, 2024
Copy link

codecov bot commented Oct 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.93%. Comparing base (440498f) to head (c7e16bc).
Report is 52 commits behind head on dev-2.x.

Additional details and impacted files
@@            Coverage Diff             @@
##             dev-2.x    #6095   +/-   ##
==========================================
  Coverage      69.93%   69.93%           
+ Complexity     17730    17729    -1     
==========================================
  Files           1996     1996           
  Lines          75402    75402           
  Branches        7717     7717           
==========================================
  Hits           52731    52731           
  Misses         19995    19995           
  Partials        2676     2676           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

doc/dev/decisionrecords/Codestyle.md Outdated Show resolved Hide resolved
src/main/java/org/opentripplanner/transit/model/package.md Outdated Show resolved Hide resolved
doc/dev/decisionrecords/Codestyle.md Outdated Show resolved Hide resolved
@optionsome
Copy link
Member Author

Through a quick google search, I found out that there might already be a maven plugin that could be used to generate package-info files for us https://github.com/bohnman/package-info-maven-plugin. It isn't the most popular or most actively developed project and I haven't tried yet if it works in practice. Is it worth trying? What do you think @t2gran @habrahamsson-skanetrafiken ?

@optionsome
Copy link
Member Author

Although seems like the maintainer has announced he has no time to maintain it and there is a new fork of it https://github.com/willhains/package-info-maven-plugin

@leonardehrenfried leonardehrenfried marked this pull request as draft October 10, 2024 08:46
@optionsome optionsome marked this pull request as ready for review October 11, 2024 13:36
pom.xml Outdated
<artifactId>package-info-maven-plugin</artifactId>
<version>1.1.0</version>
<configuration>
<!-- Couldn't get this to work for main and ext code at the same time. -->
Copy link
Member

Choose a reason for hiding this comment

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

Sorry Joel for not looking at this before, but if you want 2 executions with different config, then you create two execution blocks and move the config inside the execution. This is the default, so moving only the sourceDirectory should be enough. This is however good enough.

.gitignore Outdated Show resolved Hide resolved
t2gran
t2gran previously approved these changes Oct 16, 2024
@habrahamsson-skanetrafiken habrahamsson-skanetrafiken removed their request for review October 18, 2024 12:08
@optionsome optionsome merged commit c794227 into opentripplanner:dev-2.x Oct 22, 2024
5 checks passed
@optionsome optionsome deleted the null-annotation-conventions branch October 22, 2024 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants