-
Notifications
You must be signed in to change notification settings - Fork 52
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
cleanup lib & utils, etc. #15
Comments
Here are my findings from a quick look through what is now in
Synchronous file & process exec calls should be avoid whenever possible. I think it would be ideal to use await and async instead of Promise chains (#39). |
Hey sorry, been a bit busy but am looking at this now, have removed most of the utils. Am currently removing promises for async/await |
Thanks @dsyne for your work so far on this, no rush on my part. I already saw your I would actually like to hold off on changes such as integrating I will likely hide some of our conversation in #28 as resolved. |
…thub.com/dsyne/create-react-native-module into dev ref: #15 (cleanup utils)
Hi @dsyne, I just updated the title to hopefully match of the scope of our ongoing discussion. My response should be coming with some ideas in the next 6-12 hours or so. Thanks for your help so far. |
My apologies for the delay, I am still in the middle of a few things so you may as well park the work for now. I hope to send my response soon. Proposals, comments, and discussions are always welcome but beware that I will likely make some major changes to the JavaScript in the next 1-2 days or so. |
No problem at all, i've been away for a few days and am just catching up with things at work. I'll happily jump back on when you have things sorted so i'll keep an eye out. 👌 |
FYI you will likely see some more updates before you see my response. I hope to finish these soon, no promises yet. Another thing is that I may start to use this package to promote some of my services. I may consider promoting other people in the future, no promises though. In general, critical feedback on PRs and other proposed ideas would always be helpful. Also for draft and WIP PRs. |
Hi @dsyne, my apologies for continued lack of response. I am still pretty busy with some major updates, and in parallel with some other projects and commitments. It may be a very long time before I get organized enough to get into formal delegation, and this may never happen. I am thinking it would be more helpful if you can contribute some feedback on issues, proposals, and discussions as they come up, and maybe take a look at some "help wanted" issues. And any other proposals you can think of would be welcome for discussion and consideration. You may want to look at some recent contributions by @dlowder-salesforce for some inspiration. And I would like to thank you for recommending this project in facebook/react-native-website#1118. |
Remaining artifact was factored out of Thanks @dsyne for your offers to help. As I tried to explain before, your input and contributions would be appreciated anytime. |
I suspect most of the sources in
utils
could be replaced by existing npm packages. Maybe a limited number of new utility packages to replace the rest.related to: #14 - move some JavaScript files into
lib
subdirectoryP.S. My goal is to get rid of the
utils
subdirectory, if possible.P.S. 2: Title shows "Fixed by #150" but this cleanup was actually done through multiple changes.
The text was updated successfully, but these errors were encountered: