-
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
fix: correct palette generation behavior in Card #15429
fix: correct palette generation behavior in Card #15429
Conversation
…ng to avoid runtime errors
Perf AnalysisNo significant results to display. All results
Perf Analysis (Fluent)Perf comparison
Perf tests with no regressions
|
Asset size changesUnable to find bundle size details for Baseline commit: 2f6ebac Possible causes
Recommendations
|
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 d8ad6b4:
|
🎉 Handy links: |
Pull request checklist
$ yarn change
Description of changes
The
FluentCard
was always generating aneutralPalette
when acard-background-color
was unset (this is most cases) which is undesirable for several reasons:This PR changes the behavior to use the upstream design-system to generate the card's background, which is the correct behavior when no local overrides have been set. It also adds some null checking that prevents runtime errors.
(give an overview)
Focus areas to test
FluentCard
component.