Skip to content
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

Closed
wants to merge 1 commit into from

Conversation

mhdawson
Copy link
Member

@mhdawson mhdawson commented Jul 12, 2017

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.

@mhdawson mhdawson requested review from jasongin and addaleax July 12, 2017 21:16
@mhdawson
Copy link
Member Author

Related to nodejs/node#13988

@jasongin
Copy link
Member

more work is needed given that the n-api files now use node internals

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?

@kfarnung
Copy link
Contributor

@jasongin I could split out the changes from my PR to land it sooner.

@kfarnung
Copy link
Contributor

I opened #79 with my changes split out from #70.

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.
@mhdawson
Copy link
Member Author

Landed #79 and then rebased this PR and validated with latest version of node that has the error changes.

@mhdawson
Copy link
Member Author

@jasongin @kfarnung once I get one approval I'll land

@kfarnung
Copy link
Contributor

kfarnung commented Jul 14, 2017

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 👍

mhdawson added a commit that referenced this pull request Jul 14, 2017
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]>
@mhdawson
Copy link
Member Author

Landed as 179d135

@mhdawson mhdawson closed this Jul 14, 2017
kevindavies8 added a commit to kevindavies8/node-addon-api-Develop that referenced this pull request Aug 24, 2022
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]>
Marlyfleitas added a commit to Marlyfleitas/node-api-addon-Development that referenced this pull request Aug 26, 2022
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]>
wroy7860 added a commit to wroy7860/addon-api-benchmark-node that referenced this pull request Sep 19, 2022
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]>
johnfrench3 pushed a commit to johnfrench3/node-addon-api-git that referenced this pull request Aug 11, 2023
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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants