apicurio-registry: API date-time return value wrong
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/
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 20 (20 by maintainers)
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.
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.