Studio API docs currently identify RPCs by function name and read one parameter schema from PostgREST's Swagger 2 document. When Postgres functions are overloaded, PostgREST exposes only one overload in that document (PostgREST #1154), so Studio cannot display or generate accurate snippets for the other signatures. RpcContent.tsx already carries a TODO for this limitation.
For example, search(term text) and search(term text, limit_count integer) share /rpc/search, but the docs may show only one argument set. A user can copy a snippet for the wrong overload or never discover the other callable signature.
/rpc/{name} unchanged.search(term text) and search(term text, limit_count integer).Would maintainers prefer overload selection in the function navigation list (name(type, type)) or a signature selector within a single function page? I lean toward distinct navigation entries because each entry has a stable OID and its generated snippet is immediately unambiguous.
The user suggests improving Studio API docs to handle overloaded Postgres functions by displaying each overload as a distinct signature. This would involve using database metadata to show all function signatures, ensuring accurate documentation and snippet generation. The proposal includes design considerations for how overloads should be presented in the UI.