Repository navigation
fix: align option setter nullability with fields - #1997
Closed
Karthik H (thekarthikh) wants to merge 1 commit into
Closed
Karthik H (thekarthikh) wants to merge 1 commit into
Karthik H (thekarthikh) wants to merge 1 commit into
Conversation
Contributor
Author
|
Hi! I’m following up on this PR. Please let me know if there’s any feedback or changes needed from my side. Thank you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #1994.
Optional option fields are nullable in the generated Java API, but their builder setters did not accept null. Update the API generator to apply matching Nullable (@nullable) annotations and box optional primitive setter parameters. Regenerated the public API sources, including long -> Long handling.
Validation: mvn -pl playwright -am -DskipTests compile --no-transfer-progress