Path parameter syntax in operation id breaks client generation tool nswag

Developer Support APIs & Integrations
1

The path parameter syntax in the operation id of the APIs breaks API client genaration tool nswag studio. For example the get deals by Id is defined as

/crm/v3/objects/deals/{dealId}

The operationId is defined as

get-/crm/v3/objects/deals/{dealId}_getById

The path parameter {dealId} in that name breaks the generation as this should be a text based name. Is there something that can be done about this?

2

Hey, @thulani :waving_hand: From the HubSpot side, I do not have any documentation offering workarounds for your specific inquiry. Have you already tried reaching out to either Microsoft support or posting an issue via the repo itself?

Best,

Jaycee

3

Thanks Jaycee. I have accepted this as a solution. However being a unique scenario it is unlikely to get much traction on the NSwag Studio repo (not mantained by Microsoft). I worked around this by overriding the templating that tool offers. This was however not ideal and there are many challenges that pop up from that as well, I do wish this could be addressed in the published specs instead.