Repository navigation
fix: force value on readonly property in inherited classes - #47
Merged
Merged
Conversation
B-Galati
approved these changes
Nov 25, 2025
B-Galati
left a comment
B-Galati
left a comment
Contributor
There was a problem hiding this comment.
Perfect if you add an automatic test 👍
benconda
force-pushed
the
fix-readonly
branch
from
November 25, 2025 16:19
98f2146 to
2ecea17
Compare
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
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.
In case we have a class with inherited readonly property it fails, in my example with a messenger RunCommandMessage override:
This fix and allow to force property values on these inherited readonly properties