Support for 'bold' namespace in fonts
See original GitHub issueDescribe the feature
Support for bold
namespace in the fonts
namespace of the theme
Motivation
The reasons is getting closer to what material design showcases as ‘common weights’ in here https://material.io/design/typography/understanding-typography.html
Related Issues
No related issues
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:11 (2 by maintainers)
Top Results From Across the Web
Font.Bold Property (System.Drawing) - Microsoft Learn
Gets a value that indicates whether this Font is bold. ... Namespace: System.Drawing ... Font.Bold)) { this.Font = new Font(this.Font, FontStyle.Bold); } }...
Read more >font-weight - CSS: Cascading Style Sheets - MDN Web Docs
The font-weight CSS property sets the weight (or boldness) of the font. The weights available depend on the font-family that is currently set....
Read more >Namespace SixLabors.Fonts
FontMetrics. Represents a font face with metrics, which is a set of glyphs with a specific style (regular, italic, bold etc).
Read more >C# Font Examples - Dot Net Perls
Drawing namespace is required. Shows a font. Some notes. We use the reference returned by the Font constructor to specify typefaces in Windows ......
Read more >Add a font as an XML resource - Android Developers
The Support Library 26.0 supports fonts in XML on devices running Android 4.1 (API level 16) and higher. Note: When you declare font...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You can put any additional stuff in the theme. I don’t think it makes sense for us to add a
bold
to the default theme when we don’t use it.I see the same thing if I try to use the
DefaultTheme
from RNP. When you override the type definition for the Theme, technically the one provided by RNP no longer matches. You’ll have to either 1) not use the default theme or 2) throw a @ts-ignore on it and make sure you have fallbacks wherever they are needed.We managed to get our library to work with our custom theme (that includes a bold font and some additional color values) and the default theme by adding fallbacks to a default theme property anywhere that we used one of our custom additions, e.g.: