[python]: typeddict generating non-input types

[l0lawrence]

even if a typeddict is not used in operations it is still being generated (i.e. azure-storage-fileshare -> AccessPolicy)

[github-actions]

🎯 Issue Triage

The Python client emitter is generating TypedDict types even for models that are not used as operation inputs (e.g., AccessPolicy in azure-storage-fileshare). TypedDicts should only be generated for types that are actually used as input parameters.

Category: Bug
Area: emitter:client:python

⚠️ No reproduction provided. A minimal repro would help diagnose this issue.

🔍 Analysis

• The Python emitter's TypedDict generation logic does not currently filter by whether a model appears as an operation input type.
• AccessPolicy (azure-storage-fileshare) is cited as an example of a non-input type being incorrectly included.
• Related issues:
  • [python] tspconfig to disable typeddict auto-generation #11354 — [closed] tspconfig to disable typeddict auto-generation
  • [python] emit typeddicts in a folder /types/ to allow for patching #11356 — [open] emit typeddicts in a folder /types/ for patching

The fix likely involves checking whether a model is reachable as an input (body, query, header, path param) before emitting a TypedDict for it.

📝 Suggested next steps

• Identify the logic in the Python emitter that decides which models get TypedDicts generated
• Add a check to only emit TypedDicts for models used as operation input types
• Add a test covering a non-input model (like AccessPolicy) to confirm it is excluded

Generated by Agentic Triage