Decaffeinate - #48
Conversation
e42b830 to
d89dfc3
Compare
f97a173 to
cbcb6c3
Compare
|
@sadick254 This is ready now |
|
@sadick254 @darangi Could you take a look at this? I have some plans in my mind to improv fs-plus, which depend on this. |
|
@aminya Could you investigate what is causing the |
|
@sadick254 That is just a one-time thing that happens in Appveyor sometimes. Restart the failing jobs and it will go away. |
|
@sadick254 Are you planning to merge this? I have big plans for fs-plus. I want to reexprt the missing methods from Just as a reference, Atom maintainers were more open to decaffeination, but this seems to have changed for unknown reasons. For example, see this PR which was merged in a day atom/event-kit#38 |
|
Hey @aminya,
Right now we are quite a small team with a lot to do. We might not be able to merge PR's in a day. |
|
@aminya When decaffeinating please avoid introducing other changes. You should create separate PR's for the changes unrelated to decaffeination. |
|
I did not do that. I have actually kept my changes for future PRs. These commits that you see are my manual work to make decaffeination more appealing. When you use the decaffeinate tool, it generates some suggestions. I just applied those so the code looks succinct. These recommendations are usually these:
If you follow my commit messages, this is what I have done. |
|
I am ok with the suggestions. In this PR i see the introduction to rollup. This could have been a separate PR. Just wanted to bring it to your attention. |
|
I can move it to another PR if it helps. That is not a problem at all. We can use a new babel version by itself too. |
|
No need. I have already reviewed the changes and happy to merge it as it is. |
|
Awesome! Thanks for merging. |

This pull requests updates fs-plus without changing the API:
Verification Process
Tests are untouched to show backward compatibility! As you see all of them pass.
Applicable Issues
Release Notes