Update DefaultCompositeConfig to send the correct object when updating listeners #757
Conversation
This file contains hidden or 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
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.
Dependent views (e.g. PrefixedViewConfig and the PrivateViewConfig) look at the object being passed when there is a new config added or updated. However, currently the DefaultCompositeConfig passes the config being added/removed instead of itself. That means the PrefixedViewConfig/PrivateViewConfig will be updated to JUST the values of the added/removed config (which is either wrong, or very wrong).
This PR updates DefaultCompositeConfig to correctly pass itself.
Interestingly enough, the DefaultLayeredConfig actually just calls configUpdated (with itself) when there are equivalent such adds/removes.