Skip to content

Conversation

@nilmerg
Copy link
Member

@nilmerg nilmerg commented Sep 8, 2025

Previously attribute setters were also respected when
passing options to the constructor. So this is mostly
about backwards compatiblity, but it's useful anway,
isn't it?
Makes attribute setters effictevely useless!
@nilmerg nilmerg added this to the v0.9.0 milestone Sep 8, 2025
@nilmerg nilmerg self-assigned this Sep 8, 2025
@cla-bot cla-bot bot added the cla/signed label Sep 8, 2025
@nilmerg nilmerg marked this pull request as ready for review September 8, 2025 14:10
@nilmerg
Copy link
Member Author

nilmerg commented Sep 9, 2025

Just noticed, annotating properties is not an option (pun intended) because of inheritance when previously a callback was registered. A subclass may override the setter, which is bypassed when annotating only the property.

cc @lippserd

The attribute setters are kept for now, to ensure
backwards compatibility with code relying on them.
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.

2 participants