Skip to content

operationId collision in webhook dispatches endpoints breaks code generation for openapi-generator #2000

@bliuchak

Description

@bliuchak

Two webhook dispatch endpoints have operationId values that collide when normalized by code generators:

  • Line 11635: /v2/webhooks/{webhookId}/dispatches - operationId: webhook_dispatches_get
  • Line 11674: /v2/webhook-dispatches - operationId: webhookDispatches_get

Both IDs normalize to the same identifier (ApiWebhookDispatchesGetRequest) in Go when using openapi-generator, causing build failures. This prevents successful client generation for languages with strict naming conventions.

Proposed solution:

  1. Rename operationId for /v2/webhooks/{webhookId}/dispatches to operationId: webhook_webhookDispatches_get
  2. Keep the same operationId for /v2/webhook-dispatches - operationId: webhookDispatches_get

The API already uses this pattern for nested resources:

  • act_runs_get for /v2/acts/{actId}/runs
  • actorTask_runs_get for /v2/actor-tasks/{actorTaskId}/runs

Ref:

Metadata

Metadata

Assignees

Labels

adhocAd-hoc unplanned task added during the sprint.bugSomething isn't working.low priorityLow priority issues to be done eventually.t-core-servicesIssues with this label are in the ownership of the core services team.validatedIssues that are resolved and their solutions fulfill the acceptance criteria.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions