-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
[IAppConfig] new tests #43370
[IAppConfig] new tests #43370
Conversation
543b714
to
7b09113
Compare
7b09113
to
a1b6357
Compare
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.
Do we have to keep a deprecated test class around? Simply remove it, no?
was thinking to keep them for a while to ensure compatibility of the deprecated methods |
Signed-off-by: Maxence Lange <maxence@artificial-owl.com>
Signed-off-by: Maxence Lange <maxence@artificial-owl.com>
Signed-off-by: Maxence Lange <maxence@artificial-owl.com>
bbde51b
to
7ac3426
Compare
Signed-off-by: Maxence Lange <maxence@artificial-owl.com>
7ac3426
to
44b76cb
Compare
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.
Aside from small nitpick, and me agreeing with @come-nc that we do not really need to keep the old tests, everything looks good to me. But I do agree that we really should remove it, especially if it is not being used.
Signed-off-by: Maxence Lange <maxence@artificial-owl.com>
Signed-off-by: Maxence Lange <maxence@artificial-owl.com>
|
(failing check not related) |
isLazy()