You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let me start with "WHAT A SENSATIONAL PIECE OF SOFTWARE 😍🚀🎉"
Is your feature request related to something something in Mechanic? Please describe.
I would really love to have hooks before and after the download() and/or done()
Is your feature request related to a problem? Please describe.
What I want to achieve is to store the assets that are created by our consumers into a shared folder or something, to have track, to let them, reuse or get inspiration... actually an archive of the created visuals with mechanic (this could also be a huge feature of mechanic someday)
Describe the solution you'd like
I would rather love to add some pre/post hooks functions defined developers, into the index.js easily, that are executed at some point (done? download?)
Describe alternatives you've considered
fork the project, NAH, I didn't really considered that... I do prefer having that maintained by the core devs
Additional context
I love you all <3
The text was updated successfully, but these errors were encountered:
Hi @puria. Thanks so much for the kind comments! We have big plans of expanding Mechanic to include something like what you're describing as a native solution, but the hooks functionality seems to be a good intermediate step as an immediate solution. If you want to contribute, that would be very welcomed! If you do have time to look at this, we would suggest that you take a look and then post a quick note here on how you want to approach it, so we can have a quick discussion before you dive into the code. Let us know!
Let me start with "WHAT A SENSATIONAL PIECE OF SOFTWARE 😍🚀🎉"
Is your feature request related to something something in Mechanic? Please describe.
I would really love to have hooks before and after the
download()
and/ordone()
Is your feature request related to a problem? Please describe.
What I want to achieve is to store the assets that are created by our consumers into a shared folder or something, to have track, to let them, reuse or get inspiration... actually an archive of the created visuals with mechanic (this could also be a huge feature of mechanic someday)
Describe the solution you'd like
I would rather love to add some pre/post hooks functions defined developers, into the index.js easily, that are executed at some point (done? download?)
Describe alternatives you've considered
fork the project, NAH, I didn't really considered that... I do prefer having that maintained by the core devs
Additional context
I love you all <3
The text was updated successfully, but these errors were encountered: