design-systems
Here are 313 public repositories matching this topic...
- The issue is present in the latest release.
- I have searched the issues of this repository and believe that this is not a duplicate.
Current Behavior 😯
start adornment's position is not correct when autocomplete has a filled variant. it has an extra margin on top:
. Now that we have a useResizeObserver hook, we should use it in place of the useEffect linked above.
🤔 Expected Behavior
The ButtonGroup's current behavior should be maintained afte
-
Updated
Jun 12, 2020 - JavaScript
-
Updated
Jul 3, 2020 - CSS
-
Updated
Jun 18, 2020 - JavaScript
-
Updated
Sep 14, 2020 - Vue
-
Updated
Sep 6, 2020 - JavaScript
-
Updated
Sep 5, 2020 - JavaScript
-
Updated
Nov 6, 2019 - JavaScript
-
Updated
Sep 3, 2020 - JavaScript
One of the consumers of our system uses curly braces for content replacement in strings.
Due to the way that SD currently uses curly braces in the build process there is no way I can have a string that includes the braces for consumption.
I have tried a number of ways to escape the braces with no luck
Other languages and templating systems seem to use the concept of using double curly b
-
Updated
Aug 7, 2020 - JavaScript
-
Updated
May 20, 2019 - JavaScript
-
Updated
Aug 19, 2020 - C#
Improve this page
Add a description, image, and links to the design-systems topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the design-systems topic, visit your repo's landing page and select "manage topics."


What problem does this feature solve?
interface CascaderProps needs fields name and id
What does the proposed API look like?
export interface CascaderProps {
...
name?: string;
id?: string;
...
}