Open heyjoethomas opened 1 year ago
I came here to say the same thing. The most frustrating thing about using a new system of components is when the documentation is lacking. It's time-consuming to dig through source code to figure things out. At version 10, there should at the very least be props documentation for the sub-components that we're expected to use. 🙏
Hi! We noticed there hasn’t been activity on this issue in a while. After 30 days, it will close automatically.
If it’s still relevant, or you have updates, comment and let us know. And don’t worry, you can always re-open later if needed.
KEEPALIVE
Hi! We noticed there hasn’t been activity on this issue in a while. After 30 days, it will close automatically.
If it’s still relevant, or you have updates, comment and let us know. And don’t worry, you can always re-open later if needed.
Keep open
Hi! We noticed there hasn’t been activity on this issue in a while. After 30 days, it will close automatically.
If it’s still relevant, or you have updates, comment and let us know. And don’t worry, you can always re-open later if needed.
KEEPALIVE
Feature request summary
There are a number of Polaris components that rely on subcomponents to compose themselves or add functionality. Currently you can only see this in the code preview. But you can't see them within the actual props table or anywhere else on the documentation. If these subcomponents have props then there is no way to discover them besides going into the codebase
Rationale
If subcomponents are not exposed we are making it harder for developers to use and build confidently. They will be slowed down and will have to context switch in order to get the info they need.
Example
The example below is for the
Popover
component. We can see that there are two subcomponents being used:Popover.Pane
andPopover.Pane