talend / design-system Goto Github PK
View Code? Open in Web Editor NEWTalend Design System
Home Page: https://design.talend.com
License: Apache License 2.0
Talend Design System
Home Page: https://design.talend.com
License: Apache License 2.0
Rewrite them in TS here and proxy them in TUI
Design system rely on @popperjs-core and TUI has the previous major version of this lib.
Get the good fonts from Webpack build
Create a new package @talend/fonts to rely on
Styled components need to instantiate a ThemeProvider to get theme colors
Validation
Quality Assurance teams perform automated tests on Products for non-regression testing.
QA teams lean on HTML ID attributes or XPath to automate tests on UI, and updates on the shared library can break these scenarios.
I suggest including [data-testid]
in the components or layout markup.
1 — By documenting them, the first benefit will be to act on a contract with our QA team.
2 — By using them, after all, the second benefit will also be to perform component testing.
We need to agree on a specific vocabulary to use for their values.
I suggest this pattern: <component_name>.<element_type>.<interactive_action>
Identifier | Description |
---|---|
component_name | Component identifier from our design language (ex: modal, search, password, inlineediting, etc.) |
element_type | Element or its type used (ex: button, link, input, textarea, etc.) |
interactive_action | Interactive action as an identifier (ex: cancel, edit, submit, etc.) |
For example, for the button Edit used in the Ìnline editing
<Button data-testid="inlineediting.button.edit">Edit</Button>
Or for a search bar used as Filter
in a list
<Search data-testid="filter.input" />
In progress
Styled Components are great for managing a design system with several themes or modes.
They have been chosen because we needed multi-themes support and including IE11 support. So CSS custom properties were not an option.
We've since dropped the support of IE11. We can challenge that choice.
They intertwine styles and components in a way that muddles the component's typings.
Its as
property is too permissive for a design system, enabling users to break the intended patterns using any HTML element or React component.
There is no guarantee about the tokens you use (or not) in your styles.
You cannot quickly identify which DOM node will be generated because of the exported Styled Components.
You must precise the displayName
for each component and their variations
Try several options:
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.