[pickers] Move internal localization hook `useLocaleText` to Public API about mui-x HOT 6 CLOSED

Got it @kealjones-wk ... I will add this to the board, so we can estimate and discuss this with the team! Thanks for the clarification.

from mui-x.

@kealjones-wk could you confirm if this is some other request additional to the one discussed, groomed, and planned in #12049 (comment)? 🤔
To me, this looks like a duplicate issue at the moment. 🙈

from mui-x.

The issue has been inactive for 7 days and has been automatically closed.

from mui-x.

@LukasTy
Sorry for the delayed response i was away at a conference.

Fair enough that its a duplicate, I just wanted it to be explicit of the want as that other ticket wasn't explicitly asking for all these hooks to be public.

Also I was hoping that we could get some momentum behind this as pro/premium users because it is a large issue for my team that is actively working on DatePickers right now.

from mui-x.

Closing #12049 in favor of this more explicit issue.
We agreed to move useLocaleText hook to public API, preferably under @mui/x-date-pickers/hooks.
We agreed to add a section about using this capability/hook in the https://mui.com/x/react-date-pickers/localization/ page and link to an updated demo using it in https://mui.com/x/react-date-pickers/custom-components/#component, which should cover pain points mentioned in #12049.

from mui-x.

⚠️ This issue has been closed. If you have a similar problem but not exactly the same, please open a new issue.
Now, if you have additional information related to this issue or things that could help future readers, feel free to leave a comment.

@kealjones-wk: How did we do? Your experience with our support team matters to us. If you have a moment, please share your thoughts in this short Support Satisfaction survey.

from mui-x.