Regression on null v1.9.3 to v1.10.0
See original GitHub issueI appears there has been a behavioural change between v1.9.3 and v.1.10.0 for the following code:
console.log(numbro(null).format("0.00%"));
1.9.3 fiddle
https://jsfiddle.net/deenairn/L6bygxdw/3/
This outputs: NaN%
1.10.0 fiddle
https://jsfiddle.net/deenairn/1nywjby3/2/
This throws:
Uncaught Error: Invalid input numbro.min.js:117
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:17 (9 by maintainers)
Top Results From Across the Web
Regression on null v1.9.3 to v1.10.0 · Issue #265 - GitHub
I appears there has been a behavioural change between v1.9.3 and v.1.10.0 for the following code: console.log(numbro(null).format("0.00%"));.
Read more >scipy.stats.linregress — SciPy v1.9.3 Manual
Calculate a linear least-squares regression for two sets of measurements. ... The p-value for a hypothesis test whose null hypothesis is that the...
Read more >Chapter 15 Linear regression | Learning statistics with R
The test that we're interested has a null hypothesis that the true regression coefficient is zero (b=0 b = 0 ), which is...
Read more >Lecture notes on ridge regression - arXiv
This document is a collection of many well-known results on ridge regression. The current status of the document is 'work-in-progress' as it is ......
Read more >Changelog · Prodigy · An annotation tool for AI, Machine ...
8.5 2019-10-19. This update includes a fix for a regression introduced in v1.8.4, as well as small improvements to the dataset creation and...
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
I can remove it, it’s fine for me 😄
I think it may worth to make it configurable, like
numbro.config({ throwOnNan: true })
for cases, when developer want’s to be strict and ensure that numbro will never receive NaN.