-
Notifications
You must be signed in to change notification settings - Fork 4k
BugFix 11097: Update FontFaceDeclaration to support customizable font styles #11098
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
Conversation
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) ✅ license/snyk check is complete. No issues have been found. (View Details) |
✅ PR preview is ready!
|
sfc-gh-bnisco
left a comment
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.
Code change looks good, can we add some e2e snapshot tests for this?
|
Note to self: looks like the fonts aren't being properly loaded for the e2e tests. (Look at the f's) |
- Modified the FontFaceDeclaration component to allow for an optional `style` property in the fontFaces array, defaulting to "normal" if not provided. This change enhances flexibility in font styling for better design adaptability.
…to make it clearer that the proper fonts are being used
…own for stuff that's not needed to reduce filesize and satisfy ruff
4e54bbb to
87ce85a
Compare
Describe your changes
styleproperty in the fontFaces array, defaulting to "normal" if not provided. This change enhances flexibility in font styling for better design adaptability.Before
After
GitHub Issue Link (if applicable)
closes #11097
Testing Plan
E2E test added.
Contribution License Agreement
By submitting this pull request you agree that all contributions to this project are made under the Apache 2.0 license.