You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
.DEBUG=true is quite useful for additional validations before starting to calculate.
Right now its available via debug=true - which sounds more like something that is not supposed to run in prod.
Right now a few validations are run with it (NaN and exponentials afaik). Also, at some point maybe other debug functionalities are added, which makes me worry to use it right away.
Does something speak against a THROW_ON_NAN setting (just an example), maybe additional to the current debug mode?
All the best,
Robert
The text was updated successfully, but these errors were encountered:
Apologies for not responding at the time but I left this issue open for consideration.
I don't want to add another setting but perhaps I should have made DEBUG = true throw on NaN, and perhaps Infinity also, in the first place. I also should probably have called it STRICT mode not DEBUG.
Hi Micheal,
thanks for bignumber.js!
.DEBUG=true
is quite useful for additional validations before starting to calculate.Right now its available via
debug=true
- which sounds more like something that is not supposed to run in prod.Right now a few validations are run with it (NaN and exponentials afaik). Also, at some point maybe other debug functionalities are added, which makes me worry to use it right away.
Does something speak against a
THROW_ON_NAN
setting (just an example), maybe additional to the current debug mode?All the best,
Robert
The text was updated successfully, but these errors were encountered: