-
Notifications
You must be signed in to change notification settings - Fork 22
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
Promise-based navigation #36
Comments
Hi, I will look at it, glad that mineflayer-navigate could be useful to you
!
It was implemented before promises were a thing so indeed it was never
considered before.
However there are many users of mineflayer and its plugins so we try to
break the API as rarely as possible.
It would be great if it was possible to find a way to expose the promise
API and also keep the old API at the same place. (Without copy pasting the
code)
On a related topic, you can have a look at the mineflayer GitHub issue on
promises.
…On Mon, Dec 3, 2018, 08:58 Florian ***@***.***> wrote:
Good morning everybody,
i'am sorry for opening an issue on this; did not found an more appropriate
place for it. While working on a project using mineflayer-navigate my code
very fast became a mess because of all the events fired and holding status
objects and so on.
After a while i started to wrap this module in a promise based manner in
order to use it in a more sequential style (without loosing any of the
concurrency features), and express temporary dependencies better. This
weekend i decided to proper document my code and publish it.
Feel free to use it and it would be a pleasure if my code becomes part of
this one (i avoided a pull request, because this topic was never discussed
here, but it would be a pleasure to do so).
github: mineflayer-navigate-promise
<https://github.com/thisismexp/mineflayer-navigate-promise>
npm: mineflayer-navigate-promise
<https://www.npmjs.com/package/mineflayer-navigate-promise>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#36>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACPN_ojk80sMxum9cY5m29zTqQ7Opkumks5u1Nm0gaJpZM4Y-DgZ>
.
|
Thank you for your reply. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Good morning everybody,
i'am sorry for opening an issue on this; did not found an more appropriate place for it. While working on a project using mineflayer-navigate my code very fast became a mess because of all the events fired and holding status objects and so on.
After a while i started to wrap this module in a promise based manner in order to use it in a more sequential style (without loosing any of the concurrency features), and express temporary dependencies better. This weekend i decided to proper document my code and publish it.
Feel free to use it and it would be a pleasure if my code becomes part of this one (i avoided a pull request, because this topic was never discussed here, but it would be a pleasure to do so).
github: mineflayer-navigate-promise
npm: mineflayer-navigate-promise
The text was updated successfully, but these errors were encountered: