You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 15, 2024. It is now read-only.
Notice the first "global" parameter called list_id used as a path value, and then, on the GET definition, there is another instance of parameter list_id, but now from the query area.
The exact same issue exists for the other errors above: a global segment parameter is redefined as a specific query parameter in the individual endpoints.
These errors prevent us from loading the definition in ApiMatic and converting it to v3.0, which is a requirement for us since our client generation tool doesn't support v3.1 OpenAPI definition files.
Could this be fixed in the source, so that the same parameter name is not used across multiple areas?
The text was updated successfully, but these errors were encountered:
Ahoy! Thank you for opening your first issue here! If this request is regarding troubleshooting your application, please reach out to the support team via https://support.twilio.com. Please note that this repo accepts Issues; however external Pull Requests cannot be accepted because the code is generated using Twilio SendGrid's tooling.
Issue Summary
When running validation from ApiMatic, several 'duplicate parameter name' errors are thrown:
All of these errors occur for parameters that are present both as a segment, as well as a query string parameter. For example, from https://raw.githubusercontent.com/sendgrid/sendgrid-oai/main/spec/paths/legacy_marketing_campaigns/contacts_api_lists.json
Notice the first "global" parameter called
list_id
used as apath
value, and then, on theGET
definition, there is another instance of parameterlist_id
, but now from thequery
area.The exact same issue exists for the other errors above: a global segment parameter is redefined as a specific query parameter in the individual endpoints.
Here are the 2 places in the example above:
sendgrid-oai/spec/paths/legacy_marketing_campaigns/contacts_api_lists.json
Lines 265 to 272 in 072cebe
sendgrid-oai/spec/paths/legacy_marketing_campaigns/contacts_api_lists.json
Lines 282 to 289 in 072cebe
These errors prevent us from loading the definition in ApiMatic and converting it to v3.0, which is a requirement for us since our client generation tool doesn't support v3.1 OpenAPI definition files.
Could this be fixed in the source, so that the same parameter name is not used across multiple areas?
The text was updated successfully, but these errors were encountered: