bignum parse about frisby

[vlucas]

Yes, I agree that this should be configured through a globalSetup option.

[cstephe]

+1 I'm having issues with this as well, where sometimes when dealing with a '*' array type check frisby interprets numberStr as a number and other times it sees it as a function. I'm still tracking it down though. A sample debug is below for what its worth, It shows that the two items in the array look to be of the same type on line 598, However the first one is somehow interpreted by frisby as a function on line 1290 while the second one on line 1290 is interpreted as a number.

so far this seems to be happening only with the first item in a (*) all in array check.

line:596 all in array
line:598 json > below
{ timestamp: 1407336475931,
used: { numberStr: '2.39895984E8' },
free: { numberStr: '3.793975888E9' } }
line:1290 key:kt>used:function
line:1291 js typeof>function
line:1292 jsonTest below>
{ used: [Function: Number], timestamp: [Function: Number] }

line:598 json > below
{ timestamp: 1407336485927,
used: { numberStr: '2.73715896E8' },
free: { numberStr: '3.760155976E9' } }
line:1290 key:kt>used:number
line:1291 js typeof>object
line:1292 jsonTest below>
{ used: {}, timestamp: [Function: Number] }

[cstephe]

FYI injecting JSON for bignumJSON > bignumJSON = JSON //require('json-bignum')
Fixes my issues, However, I'm not to familiar with the use of big number, but for those with a similar problem there you go.

[vlucas]

I think I am going to just remove bignumJSON from the project. Anything that mutates the actual structure of the JSON is not a good solution IMHO. It will be removed in the next version of Frisby.

[firehist]

@vlucas Thanks a lot!