More accurate response type in OpenAPI schema

This space is made available to users of Open Patent Services (OPS) web-service and now also to users of EPO’s bulk data subscription products such as 14. EPO worldwide bibliographic database (DOCDB), 14.11 EPO worldwide legal status database (INPADOC), 14.12 EP full text data, 14.1 EP bibliographic data (EBD)and more.

Users can ask each other questions, exchange experiences and solutions, post ideas. The moderator will use this space to announce changes or other relevant information.
Post Reply

e5gs9t
Posts: 3
Joined: Sat Feb 25, 2023 10:32 pm

More accurate response type in OpenAPI schema

Post by e5gs9t » Sat Feb 25, 2023 11:00 pm

Currently, the OPS OpenAPI specification (http://ops.epo.org/wsdl/ops.yaml) defines `type: string` for a successful request (see e.g. the "Register Retrieval Service").

Code: Select all

      responses:
        200:
          description: Valid
          schema:
            type: string
Would it be possible to use a more accurate type?
Cf. https://swagger.io/docs/specification/d ... responses/

In my case that would help tremendously with auto-generating TypeScript types from the specification, especially when requests are sent with an `Accept: application/json` header.


EPO / OPS Support
Posts: 1298
Joined: Thu Feb 22, 2007 5:32 pm

Re: More accurate response type in OpenAPI schema

Post by EPO / OPS Support » Mon Feb 27, 2023 10:13 am

Hi

Thank you for your feedback, I will show that to OPS developers and see if there is anything that can do about it in future versions

Regards,
Vesna for OPS


e5gs9t
Posts: 3
Joined: Sat Feb 25, 2023 10:32 pm

Re: More accurate response type in OpenAPI schema

Post by e5gs9t » Sat Mar 04, 2023 12:15 pm

Thank you very much! Please let me know if I can be of any help.


Post Reply