Fix already bound assert for extensions #403
Open
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.
There is a following scenario:
SomeModel: RdExtBase
is created on one side of a protocolRdExtBase.init > Protocol.submitExtCreated
all listeners are invokedSomeModel.getOrCreateExtension("mySubModel")
RdExtBase.init
continues and tries to bind all itsbindableChildren
To fix this case, we can check that an extension is already bound and bound to us as a parent. Then we have no need to bind it again.