-
-
Notifications
You must be signed in to change notification settings - Fork 586
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
Disabling accessor setter when value resolution falls back to the property default value #1422
Conversation
joaojacome
commented
Aug 10, 2022
Q | A |
---|---|
Bug fix? | yes |
New feature? | no |
Doc updated | no |
BC breaks? | no |
Deprecations? | no |
Tests pass? | yes |
Fixed tickets | #1421 |
License | MIT |
d9ba369
to
47aed2b
Compare
@goetas @scyzoryck please review :) |
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.
@joaojacome Thanks for contribution! Do you think that it cause no breaking changes? Should we update documentation for this behavior?
Best, Marcin
Hello :) So, the previous MR fixing the default value for constructors had a BC, and this MR is to fix that. BUT, this |
@goetas Can you take a look at this one? Thanks! |
@joaojacome hi, I will! sorry for the delay |
…perty default value
…perty default value
…perty default value
Signed-off-by: Joao Jacome <[email protected]>
4159beb
to
55ae3c6
Compare
@goetas any chance you could tag a release? We are currently unable to upgrade beyond 3.17.1 and this PR fixes that |