Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

API date-time return value wrong

See original GitHub issue

In the openapi documentation it’s documented that you return a date-time. This is the case for meta data modifiedOn as an example at https://www.apicur.io/registry/docs/apicurio-registry/1.3.3.Final/assets-attachments/registry-rest-api.htm#operation/getArtifactMetaDataByGlobalId.

As you can guess now you return a “integer” timestamp which cases my generated client in go to fail as it’s expecting a valid date-time string format as seen at https://swagger.io/docs/specification/data-models/data-types/

Issue Analytics

State:
Created 3 years ago
Comments:20 (14 by maintainers)

Top GitHub Comments

2reactions

jsenkocommented, Feb 24, 2021

I see, sounds good. This actually results in a more decoupled deployment, so we could start there, and optionally add more integration as we go.

1reaction

EricWittmanncommented, Feb 24, 2021

I’ll leave the creation of the repository and whatnot to you guys. I think you have sufficient privs within the Apicurio GH org to do that. If not, please let me know. Once the repo is created, let @dweber019 know so they can submit a PR! 😃 😃

Thanks everyone.