unify 1-getting-started/6_object_wrap samples to implements the same logics.
#539
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
UrielCh
changed the title
1-getting-started/6_object_wrap samples to implements the same logics.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The 3 example in 1-getting-started/6_object_wrap do not implement the same addon.
Nanimplement value() as a functionNapiimplement value as a fieldnode-addon-apiimplement value() as a functionthis PR implement value as a Read and Write field and add a getValue() as a function.
the 2 accessor (set and set) and the getter are now called in the
addon.js.the 3
addon.jsfiles are now the same.