-
Notifications
You must be signed in to change notification settings - Fork 178
add support for shallow notifications #6122
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
Conversation
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.
Looks good. But yes, more tests are called for. Please add a more detailed PR description of what this change does, and also update the changelog.
@tgoyne can you please take a look as well? |
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.
Looks like a reasonable approach to me.
not sure if the problem in core factor is something I should deal with? It only points me to the |
Cyclomatic complexity is a sort of flawed metric. and how tests are defined with Catch2 (with a lot of independent test sections within a single function) is a textbook example of something that it considers very bad. It's worth taking a second look at the code when that warning pops up to see if the function needs to be refactored, but it's fine to then ignore it if the code is fine. |
currently the tests are not exhaustive enough, but I'll add it continuously, this branch is tied to this PR in realm .NET where we're trying to add notifications that doesn't react to nested property changes for efficiencies sake