@theroutingcompany/components 0.0.24-alpha.4 → 0.0.24-alpha.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -39,7 +39,7 @@ Styling is done with [styled-components](https://styled-components.com/), a CSS-
39
39
  The approach is roughly:
40
40
 
41
41
  1. A "base" styled component with shared styles: `ButtonBase`
42
- 2. Each variant in the Figma designs is a styled component 'extending' the base component: ` const PrimaryButton = styled(ButtonBase)`` `
42
+ 2. Each variant in the Figma designs is a styled component 'extending' the base component: ` const PrimaryButton = styled(ButtonBase)`
43
43
 
44
44
  - All variant are placed in an object (a map but not a `Map()`)
45
45
  - The exported takes a `variant` prop and uses it to get the right styled component from the object map
@@ -48,7 +48,6 @@ The approach is roughly:
48
48
 
49
49
  This component library is very much a work in progress and has many gaps.
50
50
 
51
- - A component that exposes the spacing design tokens in an easy-to-use, type-safe way. Usually this is called `Box`.
52
51
  - Far from all components in the Components Figma have been implemented
53
52
  - For existing component, we need more documentation. Often, design systems include a "Guidelines" or "When to Use" section" on the component doc page.
54
53
  - Tests!
@@ -135,7 +134,9 @@ Also see [Most of the time, it’s a good idea to use React context for componen
135
134
  The context should only be consumed within the library component and not exported.
136
135
 
137
136
  <figure>
138
- > [T]he context should be kept internal to the library. Allowing the naked context to be imported and handled by applications creates a brittle coupling that will easily break in future upgrades.
137
+ <blockquote>
138
+ [T]he context should be kept internal to the library. Allowing the naked context to be imported and handled by applications creates a brittle coupling that will easily break in future upgrades.
139
+ </blockquote>
139
140
  <figcaption>
140
141
  <cite>
141
142
  <a href="https://www.gabe.pizza/notes-on-component-libraries/#most-of-the-time-its-a-good-idea-to-use-react-context-for-components-that-depend-on-each-other">Notes on maintaining an internal React component library
@@ -10789,7 +10789,6 @@ const a3 = Rb, i3 = Q7, s3 = t3, l3 = r3, c3 = o3, d3 = Me`
10789
10789
  `, TA = () => /* @__PURE__ */ S(ro, { asChild: !0, children: /* @__PURE__ */ S(Yn, { label: "Close drawer", variant: "inverse", children: /* @__PURE__ */ S(lp, {}) }) }), f3 = A(jl)`
10790
10790
  width: var(--drawer-width);
10791
10791
  z-index: 3;
10792
- width: 540px;
10793
10792
  background-color: white;
10794
10793
  padding: 24px;
10795
10794
  margin: 16px;
@@ -10799,7 +10798,7 @@ const a3 = Rb, i3 = Q7, s3 = t3, l3 = r3, c3 = o3, d3 = Me`
10799
10798
  box-shadow: ${m.elevation_static_high};
10800
10799
  border-radius: ${m.border_radius_800};
10801
10800
  scrollbar-gutter: stable;
10802
- overflow: visible;
10801
+ overflow-y: auto;
10803
10802
 
10804
10803
  @media (prefers-reduced-motion: no-preference) {
10805
10804
  &[data-state='open'] {