I believe this should be rendered in the docs.

Yet we only get this link which leads nowhere 😕

If you know of any other way of annotating ActorPricingInfo.pricing_model that would render in a nicer way, I'm all ears.

Ah, so probably we will have to reach out to @barjin to update the doc tooling 👀.

Crossposting the convo we had with Honza for more reach (>two heads are better than two):

Do I understand correctly that this is some kind of a sum type of literals (something like an enum, just not an enum)? We render enums in JS like this – I think we can also attach documentation to each member.

I'm not sure how it would work in Python like you have it now, since it's all essentially a single expression… maybe with some of those Annotated generic types? Is there a Pythonic way of documenting each single Literal member?

In any case, as a user, I would appreciate documentation for each PricingModel member, at least with a link to the Apify documentation.

Yes, this is analogous to type Foo = "asdf" | "hjkl". An inline list of the possible string values would be the best IMO, we can add the link to the documentation to the pricing_model field.

I see, so you cannot use PricingModel.FREE as a runtime value, I got confused by the assignment (sth = Literal[]) syntax. I'll see what I can do regarding the expansion of the type alias to its "value" in the call site doc.