Allow to assign Node.Name
only once to avoid on-change subscriptions overhead
#344
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.
Dumps show that

Node
s' on-Name-Change subscriptions take > 11MBBut they are not used, because the Domain Model is immutable.
And the App does not use provided API to modify the built model.
In this PR I've added checking to ensure
Node.Name
is allowed to be assigned only once to non-null value.It would be better to convert it into
init
setter, but will require massive refactoring.Also:
Node
doesn't implementIChangeNotifier
anymoreNode.Name
setter beinternal