Skip to content

Conversation

timotheeguerin
Copy link
Member

@timotheeguerin timotheeguerin commented Oct 1, 2025

fix #8511 (Resolve duplicate operationId)
fix #3080 (Provide a way to configure Operation id)

@microsoft-github-policy-service microsoft-github-policy-service bot added the emitter:openapi3 Issues for @typespec/openapi3 emitter label Oct 1, 2025
Copy link
Contributor

github-actions bot commented Oct 1, 2025

All changed packages have been documented.

  • @typespec/compiler
  • @typespec/openapi3
Show changes

@typespec/openapi3 - feature ✏️

Add a new operation-id-strategy option.,> ,> - parent-container (default and previous behavior) Join operation name with its parent if applicable with an underscore,> - fqn Join the path from the service root to the operation with .,> - none Do not generate operation ids, only include explicit ones set with @operationId

@typespec/openapi3 - fix ✏️

Deduplicate operation ids that would resolve to the same one

@typespec/compiler - feature ✏️

[API] Allow using union in emitter schemas

@azure-sdk
Copy link
Collaborator

azure-sdk commented Oct 1, 2025

You can try these changes here

🛝 Playground 🌐 Website 🛝 VSCode Extension

@timotheeguerin timotheeguerin marked this pull request as ready for review October 1, 2025 20:06
@timotheeguerin timotheeguerin added this pull request to the merge queue Oct 2, 2025
Merged via the queue into microsoft:main with commit 5e9dba1 Oct 2, 2025
26 checks passed
@timotheeguerin timotheeguerin deleted the operation-id-strategy branch October 2, 2025 20:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
emitter:openapi3 Issues for @typespec/openapi3 emitter
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: openapi same name inner namespaces results in duplicate operationId OpenAPI3 Emitter could provide a way to configure operationId
3 participants