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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minimal Bubbling Observers #13991
Minimal Bubbling Observers #13991
Changes from 15 commits
1f59ecd
bab9f67
98ff396
faf63cb
4c4fc74
0b93ca2
bde5ff0
0225a42
a781188
595f621
f5a6a99
76530d5
902ec1e
3c02e79
d89c61c
33d2820
f7239bb
932630d
116b92d
e29fd6e
a6b4499
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pedantic: I'm seeing many tests like this, not just for bubbling but observer in general. Tests using counters to determine if multiple observers ran or if a subset of observers ran. This isn't the best testing because the tests can pass when they shouldn't if an observer runs multiple times or if the wrong subset of observers run.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
simple fix is a
Vec<str>
where we can push observer "labels" when they execute and then verify withvec!["obs1", "obs2"]
it's only tests so it doesn't need to be "proper"
would that be alright?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That seems correct to me. I'd rather not make this change as part of this PR. Changing the existing tests is out of scope, and I'd like to keep consistency. But I agree these tests could be improved as follow-up work.