Warning: Missing `Description` or `aria-describedby={undefined}` for {DialogContent}. if custom ID used for Description component

[NuclleaR]

Bug report

Current Behavior

If custom id used for Description component warning appears in the console

<Description id="my-id" className="text-md mt-4 text-center font-body text-accent-d" data-role="description">
  {description}
</Description>

Expected behavior

No warning in the console

Reproducible example

https://codesandbox.io/p/devbox/adoring-jennings-hnzvm9?workspaceId=ws_RwqhyAvK5BpEaJ7RcGktvy

[nayounsang]

Can I try this issue?

[nayounsang]

For the id we specify directly, it seems like we need logic to update the internal context.
Even if we specify an id now, it is only recognized as the id created through internal useId.

[nayounsang]

It's a bit of a cautionary tale, but supporting the ability to directly specify ids seems difficult because it would require a lot of codebase changes. Since you can access elements using refs when using React, team'll probably want to avoid specifying ids directly by specifying typescript types, or have users set aria to null themselves (like there's no description).
I think the former is correct, because the title would have the same problem.