Stuck on an issue?
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.
RA.EnsureNumber, RA.EnsureString, RA.EnsureBoolean
See original GitHub issueHow about some functions for coercing values if they aren’t already that type.
const ensureString = unless(isString, toString)
const ensureNumber = unless(isNumber, Number)
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (1 by maintainers)
Top Results From Across the Web
No results found
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
@guillaumearm I’d argue that it would still make sense for consistency - we wrap
Number.isNaNforisNaNfor example.We already have
ensureArrayfor exactly that.