It looks like in the full version, there is still one case where you are still accessing Array.isArray (at line 943 of dust-full-1.1.1) instead of your internal dust version of isArray.
This normally is not a problem but I tried running the compiler via Rhino and this was causing an issue. Switching it over to reference dust.isArray fixed the issue.
interesting, can you share what was the exception or error?
We use it at LI a lot and did not yet run into this.
We are using Rhino 1.7R2.
I am running it pretty standard, loading up Rhino and then adding dust and calling the compile method on my templates. If I run it against the 1.1.1 version of dust with the single Array.isArray call in there I get the following exception:
When I update it to dust.isArray all is good.
Running the compiling through Rhino we were receiving the following exception:
Once we updated to be dust.isArray everything worked.
Likely that the version of Rhino being run lacks the Array.isArray feature added in ECMAScript 5. Likely a newer version of Rhino would get you past the problem for now: https://developer.mozilla.org/en-US/docs/New_in_Rhino_1.7R3
We should support the maximun number of browsers I think.
Are we going to change the code, I mean replace the Array.isArray by dust.isArray in this case? I could make that little change so we can close this issue.
This also seems to effect IE<9
Fix for lnkedin/dustjs issue #210. All tests passed.
thanks. good to merge.
@jairodemorais @rragan for 2 more oks.