OpenAPI has incorrect entries

[neomantra]

In the course of making and using go-openchargemap, some POI queries were failing due to inconsistencies between the OpenChargeMap OpenAPI spec and the the OpenChargeMap implementation:

• UserComment: ID is int in the code but is a string in the OpenAPI YAML.

• MediaItems: ID and ChargePointID are int in the code, but they are string in the OpenAPI YAML.

You can find my modified OCM OpenAPI YAML here... In addition to the fixes here, it also adds:

• one x-go-name: ChargePoint line due to Golang generation issues
• changes the boundingbox query param from array to string as I was having issues; I think that might be me though.

I have tremendous gratitude for this project! Thank you! :heart:

[neomantra]

Found another one:

• Latitude is double in the API code but is an integer in the OpenAPI YAML

[webprofusion-chrisc]

Thanks! It would be great if you could submit a PR with the changes you think should be made. I normally manually edit the OpenAPI YAML using Stoplight studio, then when we push the update to github it automatically updates the docs page.

[neomantra]

I will be happy to — I wasn’t sure if this file was actually the correct one to modify, so thanks for the clarification.

[webprofusion-chrisc]

Thanks, yes that's the one.