and you can't ^F which strings are allowed for a particular prop in the documentation because they only document what they feel like documenting (if you really want answers ^F the source code.) When I try scanning for a prop visually there's a good chance I'll skip over it in the 70 or so props that a control supports, particularly considering that only some of those are one the page for that component which says "it also supports the props of parent components" and the parent pages say that and so forth. Never mind the things that are hidden behind slots.
Ask an LLM how to customize a control and more often or not it gives the right answer and it's more straightforward to confirm how it works and really understand it by looking at the docs and the source code given that hint.
LLMs really fall down right now at pointing out references. Microsoft's Copilot frequently answers questions correctly but I can swear I've never seen it give a correct citation for anything.
PaulHoule•7mo ago
https://mui.com/material-ui/
and you can't ^F which strings are allowed for a particular prop in the documentation because they only document what they feel like documenting (if you really want answers ^F the source code.) When I try scanning for a prop visually there's a good chance I'll skip over it in the 70 or so props that a control supports, particularly considering that only some of those are one the page for that component which says "it also supports the props of parent components" and the parent pages say that and so forth. Never mind the things that are hidden behind slots.
Ask an LLM how to customize a control and more often or not it gives the right answer and it's more straightforward to confirm how it works and really understand it by looking at the docs and the source code given that hint.
LLMs really fall down right now at pointing out references. Microsoft's Copilot frequently answers questions correctly but I can swear I've never seen it give a correct citation for anything.