tech(alias): Create a container to handle aliased values #58
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.
⚽️ Description
Revamp the way aliases are handled inside the SDK: instead of relying on double Observable just create a wrapper (
AliasContainer
) and update its content everytime the alias changes. Rest of the SDK will then do the work! 🎉🔨 Implementation details
AliasContainer
that represents a alias and its content (value)EntityNode<AliasContainer<T>>
instances instead of complexeObservable<EntityNode<T>>
ObserverRegistry
AliasObserver
is not needed anymore and we can also useEntityObserver
for aliases