Zack Litzsinger
Zack Litzsinger
It's also complicated because Fields does that layout when it renders based on its exact children, so it doesn't map well to a consumer/provider pattern as implemented currently. I would...
+1. We should keep the `disabled` prop on the `` component and just turn it into a classname on the underlying anchor.
We don't need a classname for styling, we need it to be able to assert state on when an anchor is disabled when testing.
@a-type Sorry, I meant fields.
I tried some implementations of this and eventually came to the conclusion that there are really only two valid use cases for this: splitting a Field "cell" into multiple columns...
`Field` is mostly just CSS grid, the extra sauce on top is making sure that labels and help text line up and handling the required/label callout use cases. If we...
It looks like `clean-tag` only removes out props in the prop types of styled-components. We probably want to add our own blacklist, but it's annoying to keep it out of...
As a part of implementing spacing on new components, we want to make sure that we only use negative margins for text components. For all other components, we can use...
I think some simple renaming could work, plus exposing a function that specifically invokes the function such that we end up with no margins so that you don't have to...