-
Notifications
You must be signed in to change notification settings - Fork 246
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
fix(pacmak): Support more than 255 properties for interfaces in Java #3133
Conversation
this.code.openBlock( | ||
`protected ${INTERFACE_PROXY_CLASS_NAME}(${constructorArgs})`, | ||
`protected ${INTERFACE_PROXY_CLASS_NAME}(final ${BUILDER_CLASS_NAME} builder)`, |
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.
Certainly a bit non-traditional use of a builder, but the alternative would require the fields to be mutable. Does seem fine given that this is an internal class.
…modifier) as proposed in PR review
b096517
to
fe0f118
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.
LGTM - Thank you!
Thank you for contributing! ❤️ I will now look into making sure the PR is up-to-date, then proceed to try and merge it! |
Merging (with squash)... |
@all-contributors add @ansgarm for code and bug |
I've put up a pull request to add @ansgarm! 🎉 |
Merging (with squash)... |
Resolves #3132
This is a naive approach to fix the problem outlined in #3132 – it should not be user facing and should not break anything (famous last words before CI fails). Happy for any feedback!
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.