Add flexibility to casing of `CardItem` titles
See original GitHub issueCurrently, CardItem
uppercases all characters in whatever string is passed to its title
prop. This removes some more fine-grained control from users of this component. What if I want title case? What if I want lowercase?
Ideally, this component would be able to be extended.
I am in favor of removing the case functionality whatsoever and leaving that up to the user.
Comments @fabien0102?
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Skald Spriggan Trickster Card/Item questions | BoardGameGeek
Skald Spriggan Trickster Card/Item questions ... 2) Can you add Enhance-o-stuff to a trap played with this card? ... Metal Casing: 3 uses...
Read more >Entities - Using Oracle Digital Assistant
While intents map words and phrases to a specific action, entities add context to the intent itself. They help to describe the intent...
Read more >TPlanner A flexible & powerful day/month/week/timeline/multi-day ...
A flexible & powerful day/month/week/timeline/multi-day/multi-resource & custom scheduling user interface component.
Read more >Member Notices | CU*Answers
Use F14-Print Sample to see a sample of the printed title and experiment with different spacing and casing to get the look you...
Read more >CardExchange® Help - ID Card World
CLICK HERE to view the CardExchange® Small Business Server Install Manual ... high level of flexibility when it comes to personalizing their card...
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 Free
Top 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
(oh, gosh, sorry for replying so late)
Looking at it again, it looks like the element is identical to form labels, not so much
CardItem
headings. So if we use them asCardItem
’s and then someone later changes the form label, this will grow inconsistent. Wouldn’t it be better if we made the internal form label component public and you used that for this case?Yes! Let’s do that!