Create a generated folder to store tuist helpers

[ollieatkinson]

Is your feature request related to a problem? Please describe.
As discussed in #60 we may require a place to store helper functions so that libraries may gain access to bundled resources when using static libraries, they are not included by default.

Describe the solution you'd like
Create a .tuist/generated folder and have a mechanism for writing out code using a template system. This would eventually be good for the user to be able to define their own too (maybe Sorcery, or just a basic template).

[pepicrft]

We can use Stencil for that, which is the library Sourcery depends on. Would you call it .tuist/? I'm not very convinced about using the name of Tuist anywhere in the generated objects. For example, the Swift Package Manager doesn't use spm or Swift Package Manager anywhere in the generated project AFAIK.

[ollieatkinson]

Very true - no reason to use the tuist name here, maybe just generated

[ollieatkinson]

Just keeping reference to the conversation we had on bundled resources (which started this conversation about generated code) #60 (comment)

[pepicrft]

Generated sounds good 👍. I'm looking in @esttorhe, who has experience in implementing a graph with static libraries.

[esttorhe]

This email got lost in my inbox with all the filters and redirects

Happy to help in any way I can :)

Just let me know what you need of me. I'll read the whole thread tomorrow to get up to date

[kwridan]

This is somewhat related to the thread discussion in #785 (comment)

[ollieatkinson]

We have now implemented this with ProjectHelpers