You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found that vue checks all the inject value and throw a warn when development and null. I think it's not reasonable, here is the case:
we use provide/inject mixin to maintain the z-index for some popper component.
In our standard, z-index of tip is 100, dialog is 2000. Without the mixin, it's difficult to maintain the z-index when a tip in a dialog. With the provide/inject mixin, the tip in a dialog, the index will be 2001 while we do nothing extra in css.
In this case, the inject 'zIndexBase' is not necessary. the first popper component just use it's own zIndex. But in latest vue, it throw a warn.......
Can you showcase the problem on a minimal jsfiddle?
To me it looks ilke you're looking for default values, so, as @jkzing said, I'll keep the other issue opened instead
What problem does this feature solve?
#5628
I found that vue checks all the inject value and throw a warn when development and null. I think it's not reasonable, here is the case:
we use provide/inject mixin to maintain the z-index for some popper component.
In our standard, z-index of tip is 100, dialog is 2000. Without the mixin, it's difficult to maintain the z-index when a tip in a dialog. With the provide/inject mixin, the tip in a dialog, the index will be 2001 while we do nothing extra in css.
In this case, the inject 'zIndexBase' is not necessary. the first popper component just use it's own zIndex. But in latest vue, it throw a warn.......
What does the proposed API look like?
the inject value can accept an object:
[{'key': 'keyItem', 'required': true}, 'zIncdexBase']
The text was updated successfully, but these errors were encountered: