-
Notifications
You must be signed in to change notification settings - Fork 781
[WIP] Run prism for tests #325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
I'm not opposed to a collaboration, but it looks like @tsriram is out until the 23rd. In the mean time, we will need a signed CLA in order to merge your changes. Could you please take care of that for us? |
|
@thinkingserious CLA DocuSign'ed and sent. |
|
Now passing on Node 0.12 - PR submitted to @thinkingserious what would be the chance of upping the minimum-required Nodejs version to v0.11.12 ? This provides |
|
Based on this table, it looks like we need to keep support for .10 until 12/31/16. Do you have a reference that could help us make the justification to drop support earlier? Thanks! |
|
@thinkingserious as per the table you quoted, I believe the original plan was to end LTS for Node 0.10 three months before the OpenSSL end-of-life of 31-Dec-2016, i.e. 01-Oct-2016 . This has now crept out to the end of October. |
|
Thanks @MikeRalphson! We will remove support on November 1 in that case. |
1c1c9f0 to
58ac539
Compare
|
@MikeRalphson did you run into this error when running the tests by any chance? I was testing out the changes to see if everything was working with Node.js v7. 😄 |
|
@heitortsergent No all tests passed on Node 0.12, 4 and 6. I will try and add Node 7 and see if the error appears for me. Update: all tests pass on Node 7 too. |
|
@MikeRalphson that's great! I think the error I'm seeing might be a local problem then... Do I need to run any command(s) besides |
|
@heitortsergent You shouldn't need to, no. Maybe try replacing the two instances of response.body = response.body ? JSON.parse(response.body) : response.body;in lib/sendgrid.js with try {
response.body = JSON.parse(response.body);
}
catch (ex) {}To help diagnose the issue? |
|
Hi @MikeRalphson, Once the conflicts are merged, is this one ready to go? With Best Regards, Elmer |
|
|
|
Hello @MikeRalphson, |
Refs #316
I wanted to implement this as I thought I should have working tests before looking at any other issues.
Maybe @tsriram and I could collaborate on this?
Current limitations; does not work on Node 0.10 or 0.12, which are both at or near end-of-life... (as a bonus, it does pass on Node 6, as well as 4 and iojs).
Please let me know if I'm working along the right lines.