[docs] Remove generated CSS utility component doc#48383
[docs] Remove generated CSS utility component doc#48383mj12albert merged 2 commits intomui:masterfrom
Conversation
Bundle size
Deploy previewCheck out the code infra dashboard for more information about this PR. |
LukasTy
left a comment
There was a problem hiding this comment.
Looks nice. 👍
A couple Codex suggestions:
-
Medium: docs/data/system/getting-started/usage/usage.md#L165-L174 still tells users that Box, Stack, Typography, and Grid “accept MUI System properties as props”. That directly contradicts both this PR’s rationale and the existing v9 migration guide at docs/data/system/migration/upgrade-to-v9/upgrade-to-v9.md#L23-L45, which says those deprecated system props were removed in favor of
sx. After this lands, the API pages and Box docs will be corrected, but the getting-started guide will still send users to a removed API. -
Low: skills/material-ui-styling/AGENTS.md#L120-L127 still instructs agents that Box, Stack, Typography, and Grid accept direct system layout props. Since this repo ships agent guidance for automated edits, leaving that file stale means future generated examples and refactors can keep reintroducing the obsolete behavior this PR is trying to scrub.
Assumptions
I’m assuming master is documenting v9 semantics already; that matches the migration guides checked into the repo. I didn’t find any remaining runtime consumers of cssComponent in the code paths touched by this PR, so the builder/API/LLM removal itself looks internally consistent.
f9ff70a to
0186637
Compare
Updated ~ Box, Stack, Typography, and Grid no longer need to be specifically called out anymore |
All the direct system props were removed in v9, the
cssComponentoption for the docs generator is obsolete nowCloses #48382