I think that disallowChanges() is more for user-facing API. I do what you're suggesting all the time. E.g., in a task configuration block:
disallowChanges()
consumerTask.someInputFile.set(producerTask.flatMap { it.someOutputFile })
Those properties aren't meant to be used by users, so if they mess with the properties, that's on them, Undefined Behavior.
I see, thanks!
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think that
disallowChanges()
is more for user-facing API. I do what you're suggesting all the time. E.g., in a task configuration block:Those properties aren't meant to be used by users, so if they mess with the properties, that's on them, Undefined Behavior.
I see, thanks!