feat(autofix): Fix deprecated Configuration APIs#699
Conversation
387c180 to
380a937
Compare
afe10d5 to
e719759
Compare
829e96a to
3c2f75b
Compare
b36d877 to
f1a0571
Compare
RandomByte
left a comment
There was a problem hiding this comment.
Just one nitpick, otherwise looking great!
e61bb24 to
18a9939
Compare
|
LGTM |
codeworrior
left a comment
There was a problem hiding this comment.
LGTM.
My two comments should not prevent a submit.
| // migration is currently not possible if the return value is used | ||
| // This could be optimized with an advanced migration that detects how the return | ||
| // value is used and e.g. migrates to something like | ||
| // (getAnimationMode() !== sap.ui.core.Configuration.AnimationMode.none) |
There was a problem hiding this comment.
Why can't this be replaced like this in general?
There was a problem hiding this comment.
This comment proposes that
if (Configuration.getAnimation())becomes
if ((Configuration.getAnimationMode() !== sap.ui.core.Configuration.AnimationMode.none))Now you're proposing that any usage of Configuration.getAnimation() could safely be replaced with (Configuration.getAnimationMode() !== sap.ui.core.Configuration.AnimationMode.none), right?
I guess that's correct!
There was a problem hiding this comment.
Yes, that was my proposal. But meanwhile I noticed that the code in sap/Ui/core/Configuration is slightly more complex (it checks the opposite, that none of the false values are set - depends on the evolution of the enum whether this remains equivalent).
There was a problem hiding this comment.
Resolved due being too unsafe to migrate?
|
LGTM |
8eca40c to
a21e9d6
Compare
Based on #683 and #685
JIRA: CPOUI5FOUNDATION-1038