#19705 Add `toml` syntax in backend option documentation Issue created by tgolsson Is your feature request related to a problem? Please describe. Right now all (most?) documentation for backends uses command-line syntax to show to configure options:

--python-resolves-to-interpreter-constraints="{'key1': val1, 'key2': val2, ...}"

However, most configuration is actually provided in

pants.toml

. Overriding on the command line often causes

pantsd

to restart as well, making it an inefficient pattern for general use. Describe the solution you'd like It might make more sense to focus on

toml

syntax for configuration examples in the references like we do in the manuals. Additional context From a thread on Slack:

I don't understand how to specify this option. It seems like it's supposed to be provided as an object, but AFAIK that's not possible in TOML directly? Or is this something that must be provided at runtime?

pantsbuild/pants