Keep or map to internal input attributes and query param names

[olmohake]

Adding openrouteservice to a graph i came across the following problem:

the api uses attribute and query param names like boundary.country, alternative_routes and boundary.rect.min_lon. On introspection and add command the names are transformed to camelCase i.e. boundaryCountry, alternativeRoutes, boundaryRectMinLon. As a result of this all keys including . or _ will be ignored or cause errors as the camelCased keys match none of the attribute / query params expect by the api.

[m-Bilal]

Hello @olmohake , can you please post the link to the raw openapi spec? I can't find a way to look at it from the documentation page

[olmohake]

@m-Bilal
https://openrouteservice.org/wp-json/ors-api/v1/api-doc/source/V2

[m-Bilal]

@olmohake I understand the issue, thank you for bringing this up. Unfortunately, this is not an easy or a small fix, and I can't promise that this will get picked up anytime soon. The best way to fix it would be on your end - and that is to manually change the names in the generated typescript files (both api.ts and functions.ts) to the correct ones. Once you've made changes to these files, you can use @save annotation to ensure that the codegen does not overwrite your files (more about it here)

[m-Bilal]

@olmohake Also, we've got a separate HTTP connector as well: https://github.com/hasura/ndc-http

The difference between that connector and this one is: This connector generates Typescript code that you can edit to your liking. Typically, if you'd like to make any changes in your APIs (additional business logic, compound wrapper APIs, etc) when integrating them with your graph, then this is the way to go. On the other hand, if you do not want to make any changes, then the HTTP connector would also serve you well.