-
Notifications
You must be signed in to change notification settings - Fork 188
Nullability annotations, JavaDoc, refactorings #2456
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
Conversation
0dc3443
to
2b59753
Compare
The API doc and function signatures describe what the functions do, let's describe what they do differently from what is described in the API instead of stating the obvious.
f389f23
to
8a57dcb
Compare
The API doc and function signatures describe what the functions do, let's describe what they do differently from what is described in the API instead of stating the obvious.
The API doc and function signatures describe what the functions do, let's describe what they do differently from what is described in the API instead of stating the obvious.
44243bb
to
d4abaf6
Compare
d4abaf6
to
466f8ef
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR cleans up JavaDoc formatting, adds JSpecify @nullable annotations for improved nullability handling, and refactors several API methods and unit tests (including migrating tests to Kotlin).
- Improved JavaDocs with more concise API references
- Added JSpecify nullability annotations and removed Spring-specific annotations
- Refactored tests to utilize Kotlin naming conventions and updated the build configuration
Reviewed Changes
Copilot reviewed 81 out of 81 changed files in this pull request and generated no comments.
Show a summary per file
File | Description |
---|---|
server/src/main/java/com/adobe/testing/s3mock/dto/* | Added @nullable annotations in enum fromValue methods |
server/src/main/java/com/adobe/testing/s3mock/ObjectController.java | Updated JavaDocs and added @nullable to request parameters |
server/src/main/java/com/adobe/testing/s3mock/MultipartController.java | Refactored test method names and updated tagging tests |
server/src/main/java/com/adobe/testing/s3mock/BucketController.java | Updated JavaDocs and modified region resolution logic |
pom.xml and server/pom.xml | Added jspecify dependency and configuration updates |
integration-tests/...ObjectTaggingIT.kt | Updated integration tests with Kotlin idioms |
README.md and CHANGELOG.md | Updated documentation per new API changes |
Comments suppressed due to low confidence (1)
server/src/main/java/com/adobe/testing/s3mock/BucketController.java:373
- Removing the fallback to 'region.toString()' may lead to a null value for bucketRegion if bucketMetadata.bucketRegion() is null. Consider restoring the fallback to ensure LocationConstraint is never constructed with null.
String bucketRegion = bucketMetadata.bucketRegion();
Description
Related Issue
N/A
Tasks