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: throw when entry point is null #20779

Closed

Conversation

gabrielschulhof
Copy link
Contributor

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • commit message follows commit guidelines

@nodejs-github-bot nodejs-github-bot added c++ Issues and PRs that require attention from people who are familiar with C++. dont-land-on-v4.x node-api Issues and PRs related to the Node-API. labels May 16, 2018
Copy link
Member

@addaleax addaleax left a comment

Choose a reason for hiding this comment

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

Would be nice to use node_errors.h for this, though.

@gabrielschulhof
Copy link
Contributor Author

@addaleax I've changed the text of the error message to be exactly the same as the text for regular addons, i.e. "Module has no declared entry point."

Can we replace both with a node_errors.h construction without the result being semver-major?

@gabrielschulhof
Copy link
Contributor Author

@gabrielschulhof
Copy link
Contributor Author

@gabrielschulhof
Copy link
Contributor Author

The CI failures are unrelated.

@gabrielschulhof
Copy link
Contributor Author

Landed in 9a02de7.

gabrielschulhof pushed a commit that referenced this pull request May 24, 2018
PR-URL: #20779
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
@gabrielschulhof gabrielschulhof deleted the n-api-handle-null-init branch May 24, 2018 02:16
targos pushed a commit that referenced this pull request May 25, 2018
PR-URL: #20779
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
@MylesBorins MylesBorins mentioned this pull request May 29, 2018
@mhdawson mhdawson mentioned this pull request Jul 4, 2018
@MylesBorins
Copy link
Contributor

Should this be backported to v8.x-staging? If yes please follow the guide and raise a backport PR, if not let me know or add the dont-land-on label.

gabrielschulhof pushed a commit to gabrielschulhof/node that referenced this pull request Jul 14, 2018
PR-URL: nodejs#20779
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
MylesBorins pushed a commit that referenced this pull request Aug 1, 2018
Backport-PR-URL: #21732
PR-URL: #20779
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
rvagg pushed a commit that referenced this pull request Aug 16, 2018
Backport-PR-URL: #21732
PR-URL: #20779
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Colin Ihrig <[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.

5 participants