-
Notifications
You must be signed in to change notification settings - Fork 464
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
Update to new error helper signatures in n-api #78
Conversation
Related to nodejs/node#13988 |
That work is done already in #70. Looks like it's almost ready to merge. Maybe you should wait to rebase on top of that? |
@jasongin I could split out the changes from my PR to land it sooner. |
Update to use new signatures Update copies of n-api files so they match. I've not done a direct copy because more work is needed given that the n-api files now use node internals. I have updated so that they are consistent and will build ok with respect to this specific chaange. I took this approach to minimize the time the wrapper is broken by the breaking change on the n-api side.
Landed #79 and then rebased this PR and validated with latest version of node that has the error changes. |
Yesterday I was seeing a test failure on windows with node 8.1.4, I'll take a look today and see if I can figure out what's going on. EDIT: Nevermind, it obviously won't work on 8.1.4 because the export exists but the signature is changed. LGTM 👍 |
Update to use new signatures Update copies of n-api files so they match. I've not done a direct copy because more work is needed given that the n-api files now use node internals. I have updated so that they are consistent and will build ok with respect to this specific chaange. I took this approach to minimize the time the wrapper is broken by the breaking change on the n-api side. PR-URL: #78 Reviewed-By: Kyle Farnung <[email protected]>
Landed as 179d135 |
Update to use new signatures Update copies of n-api files so they match. I've not done a direct copy because more work is needed given that the n-api files now use node internals. I have updated so that they are consistent and will build ok with respect to this specific chaange. I took this approach to minimize the time the wrapper is broken by the breaking change on the n-api side. PR-URL: nodejs/node-addon-api#78 Reviewed-By: Kyle Farnung <[email protected]>
Update to use new signatures Update copies of n-api files so they match. I've not done a direct copy because more work is needed given that the n-api files now use node internals. I have updated so that they are consistent and will build ok with respect to this specific chaange. I took this approach to minimize the time the wrapper is broken by the breaking change on the n-api side. PR-URL: nodejs/node-addon-api#78 Reviewed-By: Kyle Farnung <[email protected]>
Update to use new signatures Update copies of n-api files so they match. I've not done a direct copy because more work is needed given that the n-api files now use node internals. I have updated so that they are consistent and will build ok with respect to this specific chaange. I took this approach to minimize the time the wrapper is broken by the breaking change on the n-api side. PR-URL: nodejs/node-addon-api#78 Reviewed-By: Kyle Farnung <[email protected]>
Update to use new signatures Update copies of n-api files so they match. I've not done a direct copy because more work is needed given that the n-api files now use node internals. I have updated so that they are consistent and will build ok with respect to this specific chaange. I took this approach to minimize the time the wrapper is broken by the breaking change on the n-api side. PR-URL: nodejs/node-addon-api#78 Reviewed-By: Kyle Farnung <[email protected]>
Update to use new signatures
Update copies of n-api files so they match. I've not done
a direct copy because more work is needed given that the
n-api files now use node internals. I have updated so that
they are consistent and will build ok with respect to
this specific chaange. I took this approach to minimize
the time the wrapper is broken by the breaking change
on the n-api side.
Also note that we'll need follow on work to expose the ability to add the code
when using the wrapper but I think that is best left to a follow on PR
so that we can limit the time the wrapper is broken.