-
Notifications
You must be signed in to change notification settings - Fork 419
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
Apply NRT to all files where it can be easily applied #5867
Conversation
@@ -14,7 +12,7 @@ public static class TestingExtensions | |||
/// <summary> | |||
/// Find all children recursively of a specific type. As this is expensive and dangerous, it should only be used for testing purposes. | |||
/// </summary> | |||
public static IEnumerable<T> ChildrenOfType<T>(this Drawable drawable) | |||
public static IEnumerable<T> ChildrenOfType<T>(this Drawable? drawable) |
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.
What's with this one? Is anyone really calling ChildrenOfType()
on a null reference?
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.
Might be okay. But also may have been a weird osu! test usage (I likely would not have made this change without a good reason). Will need to run tests against this before applying.
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.
If you don't recall from memory then I'm not sure I care that much for you to go check. I was mostly curious is all.
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.
Co-authored-by: Bartłomiej Dach <dach.bartlomiej@gmail.com>
Without other bindable classes following suit, this will only lead to headaches. Noticed in an osu!-side usage.
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.
Seems good. Going to expedite merge now to minimise chances of merge conflictery here. If it turns out something goes bad we can revert in a separate pull.
Something I've had sitting around. Tested against osu! (see ppy/osu#24019).
Another pass will follow, but feel that getting this one out of the way is a good first step.