Any chance that you'd remove capitalizedWords and auto parseFloat?
See original GitHub issueThere is a fromPath
and toPath
hook that can easily handle these.
In fact, the auto parseFloat
brings some unexpected behaviours.
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Change the capitalization or case of text - Microsoft Support
To exclude capital letters from your text, click lowercase. To capitalize all of the letters, click UPPERCASE. To capitalize the first letter of...
Read more >How to capitalize or change the case of text in any app - Zapier
Here's how to automatically capitalize text properly in Word, Google Docs, and other text editors—and in thousands of other apps using Zapier's Formatter...
Read more >Change text capitalization in Pages on Mac - Apple Support
In Pages on your Mac, automatically capitalize sentences or change capitalization to all caps, small caps, title case, or start case.
Read more >How to Change Caps to Lowercase in Word - YouTube
In this video tutorial we will show you how to easily change the capitalization settings in Word.Don't forget to check out our site ......
Read more >With jQuery, how do I capitalize the first letter of a text field ...
CSS solution with "text-transform: capitalize;" is no good if you want to use the contents of the input in backend. You will still...
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
convertNumbers will be an option in the upcoming Rudy release. so this shouldn’t be a problem as both convertNumbers and capitalizeWords won’t happen by default.
convertNumbers
isn’t an option yet. I hit this because the initial path is converted to an action, and one of the parameters sometimes looks like a number, and other times it has letters in it. Anyways, when an action is dispatched from a<Link/>
(to a deeper path), then the parameter is always a string, and it forces large portions of the application to reload data because a parameter changed and is no longer===
.