Cookiecutter: Explore using Effect

[audreyfeldroy]

During the sprints, @lvh and @glyph suggested that we consider using Effect as a way to make the code more purely functional by isolating side effects.

If someone with functional programming experience could explore modifying a small portion of the Cookiecutter codebase to use Effect, that would be great. This involves:

• Learning how Effect works
• Modifying part of a file to use Effect (e.g. a function in generate.py)
• Submitting a PR to show the Cookiecutter core team
• Helping us decide whether or not it's worth the effort, extra code, and extra dependency by making a list of pros and cons

Even if the PR doesn't make it in, we promise to credit anyone who works on this for your efforts.

[glyph]

(cc @radix, the author of Effect)

[radix]

I'd be happy to review Effect-using code :) Please ping me in whatever PR introduces it.

[hackebrot]

Sorry, I'm tired and probably shouldn't comment...BUT I'm curious..

@radix Has this been tested with tox/pytest? 😁

[radix]

Also, my general advice when it comes to Effect is to try _not_ using it, while still trying to write purely functional code. You might be happy without it, but if you do need it, it will become clear where you do need it when you try.

[radix]

@hackebrot Sorry, I don't follow. What are you referring to? The Effect library? It has quite thorough test coverage and uses the py.test library.

[bejoygm]

I would like to work on this issue. I have experience with functional programming but I have never contributed in open source. Can someone help me along the way?