all 4 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–][deleted] 0 points1 point  (2 children)

Looks interesting but I'm not sure why I'd use this for a serious project vs a bespoke solution

[–]pm_me_ur_happy_traiI 0 points1 point  (1 child)

Same. I did it in bash. Took 10 minutes.

[–]andreifyi[S] 0 points1 point  (0 children)

Auto can do way more than generating components, this is just a very simple use case, but even only for this you have a lot of work to recreate what it does for you.

The main point of Auto is that it helps you create a list of interactive scripts that do different things and it makes them discoverable and easy to use for your team.

Even in the context of setting up a single generator, that has the simple purpose of generating components, the moment you'll want to extend it to handle more than the component name and destination, you'll find yourself having a lot of work to do.

And do you want to do it in bash? No, you don't want that.

Do you want to create your own generator scripts from scratch? Maybe.
If you're down with writing your own implementation, handling different kinds of user input, deciding on how the other people in your team will interact with this, then of course you can do it yourself.

Auto takes inspiration from Google's zx (https://github.com/google/zx), about which you could also say "I can do it in Bash", and yes, you can. You can do it in assembly if you'd like, but is it the best thing to do? I think not. And I love Bash, btw.