Migrate the templates to use mason package.
Closed this issue · 2 comments
XavierChanth commented
Is your feature request related to a problem? Please describe.
at_app is relatively slow, because it essentially does generation twice.
Once for flutter, then once for at_app.
Describe the solution you'd like
Use mason to build the app templates.
Describe alternatives you've considered
None so far.
I want to do a POC to see if this helps us with automation in any way, my guess is yes since we can build the mason bricks outside of at_app_templates, and use their git path instead.
Additional context
This could potentially simplify the pipeline from package examples -> at_app samples.
XavierChanth commented
Mostly completed, just need to polish the edges:
- Ensure test coverage is good
- Integrate the templates.yaml config parser to automate template building. (The pieces are there, they just need to be assembled)
XavierChanth commented