-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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: updates FluentCard to correctly resolve designSystem properties and set background-color / neutralPalette context #15509
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 c8bc6d5:
|
Perf AnalysisNo significant results to display. All results
Perf Analysis (Fluent)Perf comparison
Perf tests with no regressions
|
Asset size changesSize Auditor did not detect a change in bundle size for any component! Baseline commit: 5babd0e822f182f8a33e096e615524651ae77968 (build) |
d03fe32
to
c8bc6d5
Compare
🎉 Handy links: |
Pull request checklist
$ yarn change
Description of changes
This PR does several things:
FluentCard
to extend theDesignSystemProvider
base class instead of theFluentDesignSystemProvider
. The card was previously extendingFluentDesignSystemProvider
as a work-around to a property resolution issue that has been fixed.neutralLayerCard
recipe with the parent provider's context.backgroundColor
to either the product ofneutralLayerCard
at the parent DSP or to thecardBackgroundColor
. This is the wrong behavior because in cases where thebackgroundColor
is the product ofneutralLayerCard
, the color is a product of the upstream palette and the still-valid palette exists on theFluentCard
s designSystem object. In cases where thebackgroundColor
is thecardBackgroundColor
, there is already code to set theneutralPalette
to be a product of thecardBackgroundColor
in thecardBackgroundColorChanged()
method.Focus areas to test
FluentCard