Improve documentation for supported parameters in get_anndata() method

[hthomas-czi]

Without being familiar with the schema, it's not clear which obs columns users can selected using the obs_value_filter argument.

For example, users can use sex_ontology_term_id or human-readable sex, but that's not clear in the method signature or documentation.

Proposal

• Simplify the types for obs_coord and vars_coord in the method signature.
• Add a link to the obs Schema documentation to the obs_value_filter parameter definition.
• Add a link to the vars Schema documentation to the vars_value_filter parameter definition.

Questions

• Is it possible to syntax highlight the method signature to make it easier to parse?
• The documentation for get_anndata says:

obs_coords – Coordinates for the obs axis, which is indexed by the soma_joinid value. May be an int, a list of int, or a slice. The default, None, selects all.

However, the method signature lists many more possible types. In addition the being inconsistent, the method signature is hard to interpret.

obs_coords: None | bytes | Slice[bytes] | Sequence[bytes] | float | Slice[float] | Sequence[float] | int | Slice[int] | Sequence[int] | slice | Slice[slice] | Sequence[slice] | str | Slice[str] | Sequence[str] | datetime64 | Slice[datetime64] | Sequence[datetime64] | TimestampType | Slice[TimestampType] | Sequence[TimestampType] | Array | ChunkedArray | ndarray[Any, dtype[integer]] | ndarray[Any, dtype[datetime64]] = None,

Which is correct and can we simplify the method signature type definitions to make it easier to understand?

[pablo-gar]

@hthomas-czi I would follow your lead with with recommendations.

[hthomas-czi]

I would follow your lead with with recommendations.

I added some proposals with a couple questions for @ebezzi