Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

Working with the options semantics for the JSON schema of our `pants.toml` file. Is there any special case where an option that represents a collection won't be supporting the following types :thread:

The arrays can be:
• a string (that follows a particular syntax):
```[pytest]
extra_requirements = "+['pytest-vcr']"```
• an array:
```[pytest]
extra_requirements = ["pytest-vcr"]```
• an object (with keys being only `add` or `remove`):
```[pytest]
extra_requirements.add = ["pytest-vcr"]```
E.g. <https://www.pantsbuild.org/docs/reference-pytest#extra_requirements>

Just FWIW I don't think we have to catch and solve everything from the getgo.

But maybe go look at the options loading tests?

I think this is what <@U02KAN6061E> is suggesting as a good start to get some answers: <https://github.com/pantsbuild/pants/blob/0dec547a656617ab0f7f847d04e6c19cfae2076e/src/python/pants/option/options_test.py>