Refactor namespace organization for reactive operators #1046
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
glopesdev
force-pushed
the
issue-1043
branch
from
13816af to
5a719a4
Compare
glopesdev
force-pushed
the
issue-1043
branch
from
5a719a4 to
90939a5
Compare
glopesdev
force-pushed
the
issue-1043
branch
from
e56bdc2 to
ad5a370
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR introduces a new organization for the namespaces of reactive operators. It extends the functionality of
ProxyTypeAttributeto allow for refactoring arbitrary core operators and nested types while preserving forward compatibility of older workflows by avoiding name clashes.Fixes #1043
Fixes #1053
Fixes #1055
Fixes #1058