#20910 Soliciting opinions on a `plugin` CLI New discussion created by sureshjoshi This is mostly a screenshot-driven discussion based on some ideas I had early in my maintainer ship that I'm finally getting time to get back to. This originated as an annoyance I had that there was a lot of boilerplate to create a new plugin (the need for new plugins was largely alleviated by

adhoc_tool

). So, my idea was to have a slim CLI around the act of creating and cookie-cuttering plugin code. I've picked this back up with the start of a migration tool to help migrate in-repo plugins on breaking changes. Again, early days and just a proof-of-concept right now. https://github.com/sureshjoshi/pants-plugins/blob/e5c2a2e735621b1cc6fbfe02d8eee9215a431079/pants-plugins/experimental/migrate/rules.py#L18-L49 Below

preview

means

experimental

. I'd be interested in hearing any gripes devs have in building in-repo plugins that might be solved by a simple CLI. This does not cover something like "rule errors are hard", for which we have another solution - and there's nothing much to do here for that problem. Screenshot 2024-05-12 at 16 31 46 Screenshot 2024-05-12 at 16 31 52 Screenshot 2024-05-12 at 16 32 04 Screenshot 2024-05-12 at 16 32 15 pantsbuild/pants