Skip to content

macros: create errors fully namespaced#506

Closed
gabrielschulhof wants to merge 1 commit intonodejs:masterfrom
gabrielschulhof:full-namespace-in-macros
Closed

macros: create errors fully namespaced#506
gabrielschulhof wants to merge 1 commit intonodejs:masterfrom
gabrielschulhof:full-namespace-in-macros

Conversation

@gabrielschulhof
Copy link
Copy Markdown
Contributor

Errors in NAPI_THROW() and Co. were being thrown as Error:New(...)
but they should be thrown as Napi::Error::New(...) because the former
assumes that the user has opted to declare using namespace Napi;.

Errors in `NAPI_THROW()` and Co. were being thrown as `Error:New(...)`
but they should be thrown as `Napi::Error::New(...)` because the former
assumes that the user has opted to declare `using namespace Napi;`.
Copy link
Copy Markdown
Member

@mhdawson mhdawson left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Copy Markdown
Member

@NickNaso NickNaso left a comment

Choose a reason for hiding this comment

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

LGTM

@gabrielschulhof
Copy link
Copy Markdown
Contributor Author

gabrielschulhof pushed a commit that referenced this pull request Jul 10, 2019
Errors in `NAPI_THROW()` and Co. were being thrown as `Error:New(...)`
but they should be thrown as `Napi::Error::New(...)` because the former
assumes that the user has opted to declare `using namespace Napi;`.

PR-URL: #506
Reviewed-By: Nicola Del Gobbo <nicoladelgobbo@gmail.com>
Reviewed-By: Gus Caplan <me@gus.host>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
@gabrielschulhof
Copy link
Copy Markdown
Contributor Author

Landed in c32d7db.

@gabrielschulhof gabrielschulhof deleted the full-namespace-in-macros branch December 17, 2019 01:36
kevindavies8 added a commit to kevindavies8/node-addon-api-Develop that referenced this pull request Aug 24, 2022
Errors in `NAPI_THROW()` and Co. were being thrown as `Error:New(...)`
but they should be thrown as `Napi::Error::New(...)` because the former
assumes that the user has opted to declare `using namespace Napi;`.

PR-URL: nodejs/node-addon-api#506
Reviewed-By: Nicola Del Gobbo <nicoladelgobbo@gmail.com>
Reviewed-By: Gus Caplan <me@gus.host>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Marlyfleitas added a commit to Marlyfleitas/node-api-addon-Development that referenced this pull request Aug 26, 2022
Errors in `NAPI_THROW()` and Co. were being thrown as `Error:New(...)`
but they should be thrown as `Napi::Error::New(...)` because the former
assumes that the user has opted to declare `using namespace Napi;`.

PR-URL: nodejs/node-addon-api#506
Reviewed-By: Nicola Del Gobbo <nicoladelgobbo@gmail.com>
Reviewed-By: Gus Caplan <me@gus.host>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
wroy7860 added a commit to wroy7860/addon-api-benchmark-node that referenced this pull request Sep 19, 2022
Errors in `NAPI_THROW()` and Co. were being thrown as `Error:New(...)`
but they should be thrown as `Napi::Error::New(...)` because the former
assumes that the user has opted to declare `using namespace Napi;`.

PR-URL: nodejs/node-addon-api#506
Reviewed-By: Nicola Del Gobbo <nicoladelgobbo@gmail.com>
Reviewed-By: Gus Caplan <me@gus.host>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
johnfrench3 pushed a commit to johnfrench3/node-addon-api-git that referenced this pull request Aug 11, 2023
Errors in `NAPI_THROW()` and Co. were being thrown as `Error:New(...)`
but they should be thrown as `Napi::Error::New(...)` because the former
assumes that the user has opted to declare `using namespace Napi;`.

PR-URL: nodejs/node-addon-api#506
Reviewed-By: Nicola Del Gobbo <nicoladelgobbo@gmail.com>
Reviewed-By: Gus Caplan <me@gus.host>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
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.

4 participants