Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add thousands comma-seperation in character count messages
See original GitHub issueRelated component
Context
The current GDS content style guide states:
For numerals over 999 - insert a comma for clarity: 9,000
…however the information/error message (when over 999 characters) does not include comma separation.
Example entering 1200 characters in the Design System documentation page:
The expected message in this case would beYou have 1,000 characters too many
Alternatives
None found yet, but we are considering adding some custom JS to our service. This would modify the comma-seperation message output for screens which use Character Count component.
Additional information (if applicable)
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Reopened as was closed in error. The underlying functionality needed for this to work has been completed, but the actual changes to the character count component will happen as part of #2701 and #2805.
Another alternative (if there’s nothing left to do on this other than release i18n) could be to attach this to a Github milestone and move the card to Ready To Release. I think it’ll sit there for a while, but that might be ok?