Eric Peterson
Eric Peterson
Can you make sure you are on v0.12 and then attach an example that breaks highlighting?
Resolves https://ortussolutions.atlassian.net/browse/TESTBOX-137
I would think to start with #2 until we see that performance is an issue?
What about something like this: ``` cfc _.wrap([1, 2, 3, 4]).map(function(item) { return item * 2; }).reduce(function(acc, item) { return acc + item; }, 0); writeDump(arr.getResult()); // 20 ``` And...
Probably not. I was just tinkering with it with some cbvalidation changes.
@zspitzer Done.
Try these settings and see how far they get you: ``` { "alignment.consecutive.assignments": true, "alignment.consecutive.params": true, "alignment.consecutive.properties": true } ```
Looking at the Node library, it looks like they use a second or third parameter for header information like [API Version](https://stripe.com/docs/api/versioning) or [Idempotent Requests](https://stripe.com/docs/api/idempotent_requests). We could adopt a similar approach...
I'm not sure of the usage of that third pattern, but I think you remove that. What happens when a param named headers crops up? I think it is the...
The new Lemur Pro looks like a good option. :-)