Link to the appropriate "schema wrapper" objects in the API docs

Most of the API docs make numerous references to schema wrapper objects, for example altair.Chart.configure_axisX(), but don’t actually explain the method options or link to the appropriate wrapper object. This makes it incredibly difficult to navigate the docs without constantly using the search or having the Vega schema open in another tab. For example configure_axisX should link to altair.AxisConfig. Fixing this would make the API docs a lot more user friendly.

---

Please follow these steps to make it more efficient to respond to your feature request.

• Since Altair is a Python wrapper around the Vega-Lite visualization grammar, most feature requests should be reported directly to Vega-Lite. You can click the Action Button of your Altair chart and “Open in Vega Editor” to create a reproducible Vega-Lite example.
• Search for duplicate issues.
• Describe the feature’s goal, motivating use cases, and its expected behavior.

[joelostblom]

You’re right, I mixed up which files are autogenerated. It is only the files within the schema directory that are autogenerated. The api.py file is not (as mentioned in the maintainer notes), so you should be able to make your changes there directly.

[multimeric]

Hi @joelostblom. I’ve had a go patching the docstrings in #2610. However this only fixes the configure_X functions. For things like aggregate_X, I’d like to do the same, but it seems like altair/vegalite/v5/api.py might be autogenerated, so if I edit the docstring for def transform_aggregate, it might not be the right place. If so, where is this generated from? I can’t work it out.