Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Figma Code Connect: Bugs #17607

Open
alisonjoseph opened this issue Sep 30, 2024 · 0 comments
Open

Figma Code Connect: Bugs #17607

alisonjoseph opened this issue Sep 30, 2024 · 0 comments

Comments

@alisonjoseph
Copy link
Member

alisonjoseph commented Sep 30, 2024

Issues/Bugs from original component connect 🐞

FluidComboBox

FluidMultiSelect

Treeview

  • Figma component isn't built with nesting
  • Icon within the tree node is just a child component, not a swap icon

OverflowMenuItem

  • Figma has one Menu item component that maps to two different React components depending on the context. So we aren't able to map this.

MenuItem

  • Nested menus aren't able to be fully connected

Form

  • 2 column form isn't connected, need to figure out layouts/grid
  • form modal isn't connected

Time picker

Date picker

ProgressIndicator

Fluid components

FluidTextInput

ContainedList

UnorderedList/OrderedList

  • Nested lists are built differently in code vs. Figma.

FluidSearch, FluidSearchSkeleton

RadioButton

  • Props in Figma can be set on individual radio buttons vs. code where they are set on the group
  • labeltext, warningtext, helpermessage, warningmessage, errormessage, helpertext, errortext, label
  • Use case for ever having only one radio button? Arguable that should always use RadioButtonGroup.

FluidSelect

NumberInput / NumberInputSkeleton

Dropdown / DropdownSkeleton

AccordionSkeleton

Tabs

  • TabPanel doesn't exist in Figma
  • Similar to above, many props in Figma exist on Tabs items when in code they are set on Tabs.
  • fixed secondaryLabel isn't a property in Figma, just text. - on roadmap Can you target "Text" layers as "children"? figma/code-connect#30
  • TabsSkeleton in code refers to an entire component, in Figma it is a state on Tabs items so can't be mapped.
  • IconTab nesting bugs in dev mode in Figma

Notification

DataTable

  • Data table header doesn't exist in code
  • Size properties don't match. Figma has 'XL / LG / MD' or 'SM / XS' where code has xs ,sm, md, lg, xl. Figma requires you set the size properties on different components vs. code.
  • WIP....
  • .. coming back to this one later

Breadcrumb / BreadcrumbItem

  • noTrailingSlash is set on parent Breadcrumb in code, in Figma it is set as current property on individual breadcrumb item component(s).
  • Skeleton state in Figma is set on individual Breadcrumb items vs. in code it is the entire Breadcrumb component.
  • OverflowMenu doesn't appear to be a child of BreadcrumbItem in Figma, so can't directly pull into dev mode code.
  • Variant restriction nesting bug

Checkbox / CheckboxGroup

  • indented in Figma doesn't exist in code, has to be added via custom styles by a dev in code.
  • label in Figma can be added to any Checkbox, although would only ever be added to the first item, in code it can only be added to a Checkbox group as legendText.
  • CheckboxGroup missing horizontal variant #16486
  • In Figma you can set the component state to warn or invalid and then hide the message, this is impossible in code, if the state is warn or invalid the icon for the message always shows up.

CodeSnippet

Inline

Single

Multiline

Skeleton

  • Singleline skeleton not available in Figma

Toggle

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Status: 🏗 In Progress
Development

No branches or pull requests

1 participant