UModal necessary when programmatically using UModals? about ui HOT 2 CLOSED

This is a personal preference. Some prefer having the modal in the template so it is easier for the modal to track changes on props, others prefer having it in the script so it doesn't appear in the template.

A lot of usecases exist, and I know that for most of them, I would use a higher order component (a new component that has for root an <UModal />) so that I can reuse UModal props, and extend it with my own props.

I'm not a fan of programmatically opened modals, but I know for sure this is the most convenient way to open one or another modal depending on a condition that could be declared in a function.

Also, note that when opening modals programmatically, your modal component needs to have UModal as the root component because useModal().open() passes the props to UModal.

from ui.

Thanks @noook for your answer! I accept the idea of passing own props.

Also, note that when opening modals programmatically, your modal component needs to have UModal as the root component because useModal().open() passes the props to UModal.

That's my point: If I'm forced to have a UModal, why not take away the need to write the code? 😉

Anyhow, I will find a workaround or create a relatively empty higher order component!
Thanks for your time and continue the great work 💪

from ui.