Project solar/phase 1/forms controls#3911
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
b0faa01 to
0f7c918
Compare
a00c188 to
da9e8f6
Compare
da9e8f6 to
3fb02ec
Compare
3fb02ec to
13a1c66
Compare
13a1c66 to
6810bba
Compare
6810bba to
a00b351
Compare
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
…eckbox carbonizatin showcase examples
…s, fix linting issue
…content examples Update focus outline offset for Select carbon themes and consolidate content examples
…d preliminary theming styles for Radio
…round sizing, add hover background colors
…me styles, fix mis-matched values in generic control color tokens
…ols, add token for textarea vertical padding
dchyun
left a comment
There was a problem hiding this comment.
Sorry for the pile of comments on showcase pages 😅. A lot of them are small and repetitive. A lot of them are related to the two overarching things I saw
- The examples used for the "field" and "group" controls vary across a lot of the pages. some show some example and some show others. We should align on what examples we're showing. Or maybe are these even needed? Since they are mainly layout related and only showing base elements which have their own carbonization page?
- In a few pages the disabled/hover state is not shown, and only the default disabled state is shown
| <CodeFragmentWithCharacterCount | ||
| @maxLength={{20}} | ||
| @value="Lorem ipsum dolor sit amet" | ||
| @hasValidation={{true}} |
There was a problem hiding this comment.
| @hasValidation={{false}} |
[Issue?] This example has the label "Label + Helper Text + Character count". It doesn't mention anything about the error state, but the examples have the error state. Can this be set to false?
There was a problem hiding this comment.
[Question] Should we show an example for required/optional fields or is that captured enough in the base form elements?
There was a problem hiding this comment.
[Question] Are we missing an example here for the indicator?
There was a problem hiding this comment.
There's already examples of "required" & "optional" indicators for the Label and Legend, is that what you mean?
|
|
||
| <ShwDivider /> | ||
|
|
||
| <ShwTextH2>“Field” control</ShwTextH2> |
There was a problem hiding this comment.
[Suggestion] I've made a few comments around examples to include in the "field layout" sections. I don't have strong opinions on what examples to show but maybe we could have some consistency across the different form elements. It seems right now some show some example and some show others. Idk if it's needed to show all of the ones present in the main showcase pages but maybe we can agree on a standard set to show across all the form pages.
There was a problem hiding this comment.
Thanks, we can discuss. I think some of the examples may be excessive/redundant so we could possibly stream-line these.
|
|
||
| <ShwDivider /> | ||
|
|
||
| <ShwTextH2>“Group” control</ShwTextH2> |
There was a problem hiding this comment.
[Suggestion] Should we show a required / optional example?
Refactor and improve styling for TextInput search cancel button Fix TextInput invalid focus border color style
jorytindall
left a comment
There was a problem hiding this comment.
@KristinLBradley found a few small things, there's a lot here to go through, so I'm still kind of working on the review. Everything is looking really solid though!
| "unit": "px", | ||
| "$modes": { | ||
| "default": "{border.radius.x-small}", | ||
| "cds-g0": "2", |
There was a problem hiding this comment.
This is tricky, The Figma component uses an icon/SVG as visual representation of the checkbox control (different ones for the different states). I thought this border radius should have be 1px (the icon is kind of between 1px and 2px). However, looking at the component in code, 2px is more logical. Just noting here for the record.
There was a problem hiding this comment.
I could add a comment in the JSON. Do you think that would be helpful?
| "unit": "px", | ||
| "$modes": { | ||
| "default": "{typography.body-200.font-size}", | ||
| "cds-g0": "{carbon.typography.label01.font-size}", |
There was a problem hiding this comment.
Is this for the label? The font-size in the showcase is 12px, but from what I'm seeing in the Carbon component should be 14px.
…zation showcase examples from feedback
Co-authored-by: Dylan Hyun <dylan.hyun@ibm.com>
…ation Showcase examples
…ues with Select mutiple styles
Regenerate files in output
Co-authored-by: Dylan Hyun <dylan.hyun@ibm.com>

WIP
TODO: Go through and create new shared tokens as necessary for Carbon themes to replace hard-coded values. (in progress)
📌 Summary
If merged, this PR adds carbonized Form control components to the carbonization branch.
Previews:
TextInput: Showcase preview (Figma design)FileInput: Showcase preview (Figma design)Checkbox: Showcase preview (Figma design)Select: Showcase preview (Figma design)Radio: Showcase preview (Figma design)Textarea: Showcase preview (Figma design)MaskedInput: Showcase preview (Figma design)Toggle: Showcase preview (Figma design) (Needs updating?)SuperSelect: Showcase preview (Figma design)KeyValueInputs: Showcase preview (Figma design)🛠️ Detailed description
Related:
Formprimitives (HDS-6086) #3860👀 Component checklist
[ ] A changelog entry was added via [Changesets](https://github.com/changesets/changesets) if needed (see templates here)💬 Please consider using conventional comments when reviewing this PR.
📋 PCI review checklist
Examples of changes to controls include access controls, encryption, logging, etc.
Examples include changes to operating systems, ports, protocols, services, cryptography-related components, PII processing code, etc.