Group overloaded methods together and generate a page for them

[dsyme]

Overloaded methods are begin shown individually. By default they should be shown as a single group, with a page generated for them. Relates to #573

Example: see Expr.Call here https://fsharp.github.io/fsharp-core-docs/reference/fsharp-quotations-fsharpexpr.html

[wallymathieu]

This seems like a nice thing to have. It seems to be more of an enhancement than a bug though.

[github-actions]

🤖 This is an automated response from Repo Assist.

Reviving this thread with an implementation analysis, since this issue has had no updates since 2020.

What's being requested

Group overloaded methods (e.g. multiple Expr.Call signatures) into a single entry in the member list, with their individual overloads accessible either inline or via a dedicated sub-page.

Current behaviour

Each overload is listed as a separate member entry with its full signature. For heavily-overloaded types (e.g. Array.map, String.Format, or F# quotation expressions), this creates a lot of repetition and makes the page hard to scan.

Where the relevant code lives

• src/FSharp.Formatting.ApiDocs/GenerateModel.fs — ApiDocMember list is built per FCS symbol; grouping would happen here, probably by member CompiledName/DisplayName.
• src/FSharp.Formatting.ApiDocs/GenerateHtml.fs — renders the member table/list; would need a grouped rendering mode.

Implementation sketch

1. In GenerateModel.fs (or a new pass), group ApiDocMember entries that share the same name and kind (method vs. property etc.) into an ApiDocMemberGroup.
2. In the HTML generator, render each group as a single row/section with an expandable overload list (similar to how docs.microsoft.com collapses overloads under one heading).
3. A dedicated overload page could be generated per group (e.g. reference/mytype.html#Call with anchor), matching the fsharp-core-docs style you linked.

Complexity

This is a non-trivial feature — it touches the core model, HTML generation, and potentially URL generation. It's also a potentially breaking change for anyone deep-linking to individual overload anchors. An opt-in MSBuild flag (e.g. (FsDocsGroupOverloads)true(/FsDocsGroupOverloads)) would be the safest approach.

Happy to attempt a PR for this if there is maintainer interest — it would be a good follow-on to the recent API-docs improvements (#590, #591).

Generated by Repo Assist

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@da02dddebe71d9a937665abdcd1f5214dab852a7