Would `pants designer` be worthy of the survey? :t...
# random
e
Would
pants designer
be worthy of the survey? 🤔 I can never tell when I’m in 🧌 mode or 🔥🧠🔥 mode. So sad.
Copy code
$ pants designer --help

Usage: pants designer <template name> <path>

Description: designer applies a template starting at the path, which must be an empty or non-existant folder.
It will then create the scaffolding needed for your app, library or project. Templates can be as simple
as a single app, or as complicated as full layout for a "polylith" based design philosophy.

Prebundled templates can be used to get new people started using pants in their repo and using online tutorials.
And given my day job doesn’t use a monorepo anymore, this might already be a thing and I just haven’t left #random to find out.
c
no that’s 🧠 so please submit 🙂 (will be at least the second one, as I’ve already done the same 😉 )
😁 1
p
Sounds kind of like cookie-cutter, but probably more intelligent (because pants just adds sensible magic to it all)
e
I loathe cookie cutters. They make you dumber and paper over boilerplate that should be fixed. That said, people love this in general - I'm sure the community as a whole will be happy to +1 this.
1
😂 2
p
I want something smarter that can update stuff, not just initially create it.
c
I see what you mean @enough-analyst-54434 the benefit I see being to hit the ground running, and first later when there’s some issue will you have to go back and figure all this out eventually anyway; at which point you’re hopefully in a better position to make sense of it all. So it helps lower the barrier of entry for new devs and papers over the boilerplate for seasoned ones saving a few keystrokes and brain cycles (we ought to see there’s boilerplate to reduce regardless) +1 for using something smarter than cookie-cutter that allows you to update and reapply the template in-place. I’m toying with the idea of using hof as that is one of the selling arguments for it, just hoping it will be possible without too much exposure to the CUE syntax, as that’s rather awkward to get into unless you’re nerdy enough 😉
e
As discussed in slack#random, this feature would have two goals: (1) help beginners get basic code layout right for their company’s monorepo, and (2) help create monorepo wide standard starting places for code (e.g. common API language, or CLI layouts).