From bdea2d46c328abd090f6e053c8cd67b192f21959 Mon Sep 17 00:00:00 2001 From: Mike Odnis Date: Sat, 9 May 2026 10:15:17 -0400 Subject: [PATCH] feat(nav): add Python entry under "Generated API Reference" MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Single-line nav addition — points at sdks/python/api/README which Mintlify resolves via the existing .md file. No file renames; the auto-generated trees stay as .md because Mintlify's .md link resolver is filesystem-based and already accepts the cross-references TypeDoc / DefaultDocumentation / pydoc-markdown emit. Renaming the READMEs to .mdx (attempted in earlier commits 4e31133 / 7301dbce / 54934eff) was the wrong move — .mdx parents have stricter link resolution that requires every link target to be nav-registered, which is not feasible for 3500+ auto-generated pages. The "is referenced in docs.json navigation but the file does not exist" warning that mint dev emits for .md-extension README references is cosmetic; Mintlify still renders the page. The "Generated API Reference" group from PR #17 only had TypeScript and .NET sub-groups; PR #18 (Python template) and the resulting auto-PRs (#19, #20) landed the Python content after that PR was opened. --- docs.json | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs.json b/docs.json index 1b277c15..53c16297 100644 --- a/docs.json +++ b/docs.json @@ -78,6 +78,12 @@ "pages": [ "sdks/dotnet/api/README" ] + }, + { + "group": "Python", + "pages": [ + "sdks/python/api/README" + ] } ] }