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

n-api: factor out calling pattern #36113

Closed
wants to merge 3 commits into from

Conversation

gabrielschulhof
Copy link
Contributor

Factor out how we handle a napi_status-valued return internally.

Signed-off-by: Gabriel Schulhof [email protected]

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines

Factor out how we handle a `napi_status`-valued return internally.

Signed-off-by: Gabriel Schulhof <[email protected]>
@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/n-api

@nodejs-github-bot nodejs-github-bot added c++ Issues and PRs that require attention from people who are familiar with C++. node-api Issues and PRs related to the Node-API. labels Nov 13, 2020
@gabrielschulhof gabrielschulhof requested review from addaleax, Qard and mhdawson and removed request for addaleax November 13, 2020 21:21
src/js_native_api_v8.h Outdated Show resolved Hide resolved
v8impl::V8NameFromPropertyDescriptor(env, p, &property_name);

if (status != napi_ok) {
return napi_set_last_error(env, status);
Copy link
Member

@legendecas legendecas Nov 15, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

STATUS_CALL simply returns on non-napi_ok without calling napi_set_last_error. The behavior seems not equivalent with the change. Is this intentional?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@legendecas yes, it is, because it is assumed that whichever call returned non-napi_ok did so via return napi_set_last_error(napi_<not_ok>); I checked to make sure that was the case in all locations where I made the change.

Remove semicolon from macro definition

Co-authored-by: Anna Henningsen <[email protected]>
@nodejs-github-bot
Copy link
Collaborator

gabrielschulhof pushed a commit that referenced this pull request Nov 16, 2020
Factor out how we handle a `napi_status`-valued return internally.

Signed-off-by: Gabriel Schulhof <[email protected]>
PR-URL: #36113
Reviewed-By: Stephen Belanger <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
@gabrielschulhof
Copy link
Contributor Author

Landed in 2fd2235.

@gabrielschulhof gabrielschulhof deleted the status-call branch November 16, 2020 05:52
codebytere pushed a commit that referenced this pull request Nov 22, 2020
Factor out how we handle a `napi_status`-valued return internally.

Signed-off-by: Gabriel Schulhof <[email protected]>
PR-URL: #36113
Reviewed-By: Stephen Belanger <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
@codebytere codebytere mentioned this pull request Nov 22, 2020
BethGriggs pushed a commit that referenced this pull request Dec 9, 2020
Factor out how we handle a `napi_status`-valued return internally.

Signed-off-by: Gabriel Schulhof <[email protected]>
PR-URL: #36113
Reviewed-By: Stephen Belanger <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
BethGriggs pushed a commit that referenced this pull request Dec 10, 2020
Factor out how we handle a `napi_status`-valued return internally.

Signed-off-by: Gabriel Schulhof <[email protected]>
PR-URL: #36113
Reviewed-By: Stephen Belanger <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
@BethGriggs BethGriggs mentioned this pull request Dec 10, 2020
BethGriggs pushed a commit that referenced this pull request Dec 15, 2020
Factor out how we handle a `napi_status`-valued return internally.

Signed-off-by: Gabriel Schulhof <[email protected]>
PR-URL: #36113
Reviewed-By: Stephen Belanger <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c++ Issues and PRs that require attention from people who are familiar with C++. node-api Issues and PRs related to the Node-API.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants