wide-midnight-7859802/07/2023, 2:14 PM
Now, the only real reason I bring this up is because it ties into my shell completions thing that never really found a home, but fits alongside the schema creation. Uses help to generate a file as a result of processing said help: https://github.com/pantsbuild/pants/issues/16315 This whole thing ran into the problem of
./pants help json-schema > "pantsbuild-$(./pants version).json"
not being a great place as of today, because it's mostly for venvs, and bloating the API with a custom
felt messy, and etc etc I guess the question is, since we'd have 2 items that rely on help to generate some sort of custom output files, is there a better location or a consolidation for this? If we end up as
being the play, then I'd also put
pants help json-schema
in there too
pants help completions
proud-dentist-2284402/07/2023, 3:17 PM
./pants help-export json-schema
That is similar to
./pants help-export completions
wide-midnight-7859802/07/2023, 3:33 PM
Buuuuut, it is related to intellisense/auto-complete, so ... you know... "help-ish"
happy-kitchen-8948202/07/2023, 5:24 PM
reads as "help for the json-schema subsystem or target type" which is not what this is...
./pants help json-schema
proud-dentist-2284402/07/2023, 10:45 PM
./pants export-pants-meta json-schema
./pants export-pants-meta completions
wide-midnight-7859802/07/2023, 10:52 PM
- but I'll take anywhere to put it 🙂
./pants export completions
proud-dentist-2284402/07/2023, 11:09 PM
makes more sense for both json-schema and completions than under
happy-kitchen-8948202/08/2023, 1:21 AM
could work, but then how do we say "the thing I want exported is completions, not venvs"
wide-midnight-7859802/08/2023, 1:40 AM
goal. To me, it seems that the
goal is a reasonable place for an overhaul - but I think one of the problems here was that we didn't have access to
from the non-builtin goals? Memory is a bit foggy on that part.