How should we approach sharing generic templates with the community? about sourcery

[krzysztofzablocki]

Was about to write about this, you beat me to the punch.
I think a reasonable approach would be to:

• Add a folder for generic Templates in this repository
• Add generation tests to always keep Templates up-to date with tool version thus avoiding breaking them with updates
• Bundle templates with the binary distribution of the Pod, so that people can use our default implementation if they wish

Makes sense?

[krzysztofzablocki]

I updated our readme and introduced some example templates which we might tweak, once we approach 1.0 release we can embeed those that are the most generic, take a look at #123

[bejar37]

I think it would be really interesting to have a project that people can pull in as a dependency (like SwiftGen, via Cocoapods or Carthage) which provides some basic templates for protocols like AutoEquatable or AutoHashable.
Do you think this is feasible? Another future direction for that would be providing a way for each user of that repository to add their own templates that are less widely applicable (maybe JSON parsing, lenses, etc.).

Basically, I think it would be cool for the example templates in #123 to be usable for an end-user. I'm not sure if that belongs in Sourcery itself, or in a project which has Sourcery as a dependency.

[krzysztofzablocki]

@bejar37 that's the idea, I made those files separate so we can bring them in as embedded templates later on, I didn't bundle them yet because we are far from 1.0 and a lot of changes are happening

[bejar37]

Oops, I see that I hadn't read your previous comment throughly @krzysztofzablocki . Sorry!

[krzysztofzablocki]

Actually, lets embeed them in binary distrubtion, people can choose to use them or not :)