-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
[web-components] refactor color recipes for DI #18199
[web-components] refactor color recipes for DI #18199
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 166aff3:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My only comments are that there's a large amount of what appears to be duplicative code with fast-components. Should any of this be moved into foundation? Some of it seems like primitives e.g. Palette. Also, what was our reason for making the recipes internal? Is that a temporary thing that we plan to lift after we work out a few more things?
@@ -0,0 +1,32 @@ | |||
# FAST Color Recipes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# FAST Color Recipes | |
# FluentUI Color Recipes |
@@ -0,0 +1,32 @@ | |||
# FAST Color Recipes | |||
|
|||
Color recipes are named colors who's value is algorithmically defined from a variety of inputs. `@microsoft/fast-components` relies on these recipes heavily to achieve expressive theming options while maintaining color accessability targets. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Color recipes are named colors who's value is algorithmically defined from a variety of inputs. `@microsoft/fast-components` relies on these recipes heavily to achieve expressive theming options while maintaining color accessability targets. | |
Color recipes are named colors who's value is algorithmically defined from a variety of inputs. `@fluentui/web-components` relies on these recipes heavily to achieve expressive theming options while maintaining color accessibility targets. |
**Example: Creating a SwatchRGB** | ||
|
||
```ts | ||
import { SwatchRGB } from '@microsoft/fast-components'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
import { SwatchRGB } from '@microsoft/fast-components'; | |
import { SwatchRGB } from '@fluentui/web-components'; |
bbec96d
to
166aff3
Compare
* add color-vNext folder with recipes and update specs * Change files
* add color-vNext folder with recipes and update specs * Change files
* add color-vNext folder with recipes and update specs * Change files
* add color-vNext folder with recipes and update specs * Change files
* add color-vNext folder with recipes and update specs * Change files
* add color-vNext folder with recipes and update specs * Change files
Pull request checklist
$ yarn change
Description of changes
Creates vNext color recipes and updates tests to ensure parity.
Focus areas to test
(optional)