shadcn-syntax-dialog

Your shadcn Dialog freezes when the controlled state contract is broken; you must pair the `open` prop with `onOpenChange` to allow Radix to update the state. Using `defaultOpen` is only for one-shot uncontrolled workflows.

To keep a form-in-dialog open during validation errors, close the dialog only after successful submit. Trigger `onOpenChange(false)` strictly inside the form's success callback rather than on standard submit.

Fix shadcn Dialog accessibility errors by always rendering a `DialogTitle` component. If your design omits a visible title, use an sr-only `DialogTitle` and set `aria-describedby={undefined}` when omitting `DialogDescription`.

DialogClose asChild Slot multi-child crashes occur because the Slot component expects a single proper focusable child. Avoid ref and prop swallowing issues by ensuring your `DialogClose` wraps exactly one element.

Resolve shadcn Dialog portal and z-index bugs by relying on `<DialogContent>`’s internal `DialogPortal` for auto-portal rendering. Use an explicit `DialogPortal container` only when you need a custom mounting node.

Yes, you can use react-hook-form inside a shadcn Dialog by enforcing Radix-controlled state contracts. Ensure your form submit handler manages the `onOpenChange` state correctly to close only after successful validation.