-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Disallow write-only task properties #9341
Comments
This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution. |
This issue has been automatically closed due to inactivity. If you can reproduce this on a recent version of Gradle or if you have a good use case for this feature, please feel free to reopen the issue with steps to reproduce, a quick explanation of your use case or a high-quality pull request. |
I think we want to do this eventually. |
Another good validation to add for 7.0. |
I tried to implement this, but it doesn't make much sense in the end. We also have tasks that have setters without getters, and in general there should be nothing wrong with having differently setters for properties if the different names add useful context. |
E.g.
(see
ValidateTaskPropertiesIntegrationTest#report setters for property with mutable type #type
)It should warn about a write-only property, i.e. unpaired get/set.
See: https://github.com/gradle/gradle/pull/9324/files#r280388131
The text was updated successfully, but these errors were encountered: