Jan Potoms

No, it's a feature request and the current consesus is to not implement it.

I think if we want to show code, we need to clearly show the connection it has with the UI. Otherwise I think it will only confuse the audience. IMO...

For inspiration: In Toolpad we wrote [a hook](https://github.com/mui/mui-toolpad/blob/16fed82b4851b98767cad28b7921db9efc84def1/packages/toolpad-utils/src/hooks/useStorageState.ts#L92) that handles initializing state from localstorage on the first render correctly (i.e. doesn't need an effect to run). It also syncs this...

Yes, I'll clean it up a bit and move to `@mui/utils` 👍

> To be noted that @mui/utils is a "private" npm package. Only MUI System and Base UI are supposed to import from it. This package exists so that MUI System...

> What would prevent us from following semver? Nothing prevents us, it just adds overhead. It needs to be properly maintained, backwards compatibility needs to be guaranteed more tightly, and...

I [ported](https://github.com/mui/material-ui/pull/41096) the hook to `@mui/utils`. For now with the purpose to only use it internally. If anyone has objections to this, please comment on the PR. To build save/store...

Yes, it seems to happen when I click the text itself, or the vertical center in the whitespace left of the text, basically anything in this area: ![Screenshot 2023-07-25 at...

I also updated the issue with 4. and 5. that I ran into.

> * Adding a new term for a component when instantiated on the page seems like an unnecessary complication The distinction between "template" and "instance" is a very natural one...