Consider removing dplyr and possibly purrr dependencies?

[jimhester]

dplyr is a very heavy dependency which makes using styler on CI services such as travis or appveyor problematic.

Doing this would be useful so you could style the package as a CI step and ensure there are no changes as a way to verify that PRs conform to the style. But this will only work well if styler has limited (and light) dependencies.

If you are open to the possibility of removing the dependency I could work on a PR.

[krlmlr]

I think removing dplyr and using compat-purrr.R is a good plan. Happy to review a PR.

[lorenzwalthert]

I think since I know the project fairly well by now, I can start working on this in about two weeks if @jimhester is ok with that. If I remember correctly, the majority of dplyr calls was already removed with #90, so it should not be too much of work.

[jimhester]

I have a WIP at #182.

I also realized that tidyr also has a dplyr dependency, so we would need to remove tidyr as well.

[lorenzwalthert]

Yes, that might be tricky. Especially for creating the nested parse data - as the name says - we heavily rely on tidyr::nest().

[jimhester]

tidyr wasn't bad #183

[jimhester]

dplyr (#182) is complete now as well. Purrr is fairly light these days, we can remove it if we want, but probably not really needed.

[krlmlr]

Should be good now.