When used as a library, return a Promise #46
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 main function
obj23dtiles(objPath, outputPath, options)used to returnundefined, although there is much asynchronicity properly used inside of it. Because of this, it was not possible to properly wait on completion -- the only option would be to spawnnodein a child process and wait for it to exit.This pull request makes the relevant Promise to be returned outside, so that it is possible to just
await obj23dtiles(...).Note, other issues may arise from
process.exitbeing used in the library code. Such calls should be moved tobin/obj23dtiles.jssolely but I tried to keep this pull request as humble as possible.