29 Commits

Author SHA1 Message Date
jos
a2ae756fd1 Remove semicolons 2018-10-31 21:18:51 +01:00
jos
247aeabffa Refactor all unit tests to ES6 import/export 2018-10-31 21:17:23 +01:00
greenkeeper[bot]
c5971b371a Update standard to the latest version 🚀 (#1226)
* chore(package): update standard to version 12.0.0

* update to new lint version with --fix

I believe this mainly adds whitespace to `{}`'s.

* Replace assert.equal with assert.strictEqual

This breaks a lot of tests which I will endevour to fix in the next
commits.

* Fix most errors due to assert.strictEquals

Some instances of `strictEquals` are replaced by `deepEquals`.
`toString` has been used to make some string comparisions explicit.
Tests will still fail untill #1236 and #1237 are fixed.

* Fix assertion erros due to -0

With node 10, assert.strictEqual no longer considers `0 === -0`.
I missed these first time round as I was using node 8.

* Put toString correct side of bracket

I was converting the constructor to a string rather
than the result of the computation. Oops.

* Fixed #1236: quantileSeq has inconsistant return

* Update package-lock

* Fixed #1237: norm sometimes returning a complex number instead of number

* Fix cli tests

* More changes for standardjs, and fixes in unit tests
2018-09-08 16:33:58 +02:00
ssaket
5b60ff9231 added test case 2018-06-15 12:32:58 +05:30
jos
e844004cbf Removed redundant escape characters 2018-06-13 21:15:10 +02:00
jos
0583771e4e Cleanup unused variables and imports 2018-06-13 17:25:51 +02:00
jos
1f0a37a0cb Split initialized 'const' declarations into multiple statements 2018-06-13 15:31:37 +02:00
jos
17f07ec098 Fixed incompatibility with v4 (index.js file) 2018-06-13 14:02:50 +02:00
jos
b3b96749bf Refactored var into const/let, and removed a lot of semicolons 2018-06-13 12:21:14 +02:00
jos
024b2a9e26 Fix most lint errors using npx standard --fix 2018-06-10 20:28:27 +02:00
jos
635cd0b574 Revert using /lib/ in tests, use /src/ again. Fixed coverage testing. WIP 2018-06-06 22:11:52 +02:00
jos
79071b5e4f Fixed npm run test:browser not working (WIP) 2018-06-06 21:30:41 +02:00
jos
0c084b8e20 npm test working now 2018-06-06 15:36:36 +02:00
jos
f87ec1c6db Setup Babel compilation (WIP) 2018-06-06 14:31:33 +02:00
jos
68b5e3ffe6 Released v5.2.0 2018-05-02 10:05:16 +02:00
jos
bf3f62b564 Upgraded to typed-function@1.0.0 2018-02-20 20:59:05 +01:00
jos
4469f6bd0c Remove support for implicit conversion of null to 0. See #830. 2018-01-23 20:26:38 +01:00
Gulfaraz Yasin
f42f7feffc static implementation of complex comparision 2017-06-05 11:58:27 +05:30
Gulfaraz Yasin
eda65d2228 used different approach for comparing complex numbers - resolves #837 2017-06-04 22:29:55 +05:30
jos
0cd4352856 Added automatic conversions from boolean and null to Fraction and conversions from Fraction to Complex 2016-03-14 21:24:29 +01:00
Robert Eisele
cb653ab42e Fixed parse tests 2016-02-11 04:28:09 +01:00
jos
6e1521d2a4 Use EPSILON of math.js and update on changes in config of math.js 2016-02-09 09:27:45 +01:00
jos
196c7175a3 Fixed a few more failing unit tests (related to fromPolar) 2016-02-09 09:17:55 +01:00
Robert Eisele
e6d4e40d7c Changed some tests to match new requirements 2016-02-07 14:57:02 +01:00
Robert Eisele
fcfd43a218 Added complex.js 2016-01-29 01:56:06 +01:00
jos
189d8e4918 Internal functions Unit.parse and Complex.parse now throw an Error instead of returning null when passing invalid input 2015-08-10 21:45:48 +02:00
jos
d81fe279cc String input is now converted to numbers by default for all functions. Adding two strings will no longer concatenate them, but will convert the
strings to numbers and add them.
2015-05-19 22:18:40 +02:00
jos
3242cd8550 Attached properties like.type === 'Complex' and .isComple to all data types 2015-05-05 14:35:45 +02:00
jos
7e3eda8603 Moved all data types and their construction functions into a folder of their own under ./lib/type 2015-05-05 13:51:24 +02:00