traefik / faency Goto Github PK

active is no a correct value for the NavItem variant property:

 <NavItem variant="active">

The background should be transparent instead

Dark Theme

Light Theme

It's getting flex-direction: column until the width is 768px, when it should get this value only until 767px.

Extend the Card functionality to have an onClick handler or create another component that derives from Card and has an onClick handler prop.

Add a website for the documentation

Blcoked by #114

should be:

instead of:

Design a switch button to use as a toggle

First potential use case, Theme Switcher for the Faency docs website:

related to #51

Dark Theme

Light Theme

When we have a truncated element, we could centralize the tooltip arrow based on the width of the visible part of the element.

This is causing inconsistencies in the documentation when using the dark theme.

The initial proposed solution by Mattieu is to use a design system config with static colors and have theme files consuming the design system config.

Additional information

Note: textColor="white"

Dark theme

Light theme

We should be able to specify an as property on a component in a way that it's rendered using a different Primitive that it usually should use. For some reason, it's not possible to do this in some places.

Add the Switch component to the Fæncy library.

Design #73.

Design #54.

I needed to comment a test that used the Menu component because it was not being rendered on the snapshot generated by Jest.
This is probably some limitation on Jest or some incomplete test configuration since the component is working on other places.

Based on what was discussed on #91, we should have a component to render props values nicely, according to their type.

For now, we can have the support for the following types:

• string
• number
• boolean
• color

Design #58.

CSS-in-JS is such a pain and disgusting IMO

When writing components, I faced the issue that it's not possible to use React Eva Icons inside of the components, by showing them based on Variants for example.

This issue is to find a way to do that or understand exactly why it's not possible.

Design #57.

I had to remove the placeholder test file for this component due to a Jest error on importing the react-arrow-nav library.
The InputTags components should have the feature of navigation by arrow keys when a list of options is provided.

Also, there's a possibility to use the Menu component instead of rendering a custom Menu, which would remove the need to use the react-arrow-nav lib, but this must be done carefully to keep the visual specifications.

Dark theme

Light theme

react-eva-icons should be a faency devDependency because this lib is only used in a .story file.

Dark theme

Light theme

Dark theme

Light theme

We can use the already designed switch component, but if we want to invest some time on it, here's an idea:

From here.

Should be:

instead of: