On Mon, Aug 12, 2019 at 11:16 AM Thilini Shanika <thili...@wso2.com> wrote:
> > > On Mon, Aug 12, 2019 at 10:53 AM Rukshan Premathunga <ruks...@wso2.com> > wrote: > >> Hi All, >> >> ATM generated API definition is in swagger 2. Can we make it OAS 3 for >> the new APIs? >> > Yes, we can change the default version of a newly created API to OAS > 3.0.0. However, the API creator is allowed to pick the OAS version(OAS 2 or > 3) of the API during API creation time. Are you suggesting to remove the > default support for OAS 2.0(For newly designed APIs)? > Yes, my suggestion is, if a user doesn't have an OAS definition, generate an OAS 3 definition for them. If they have an OAS definition, allowing them to import OAS 2 or 3 definition. So we will maintain the same OAS version afterward. > When new API is created from an OAS 2 or 3, we can create from the same >> imported version. Existing API also can be kept as an existing version. >> >> Thanks and Regards >> >> -- >> Rukshan C. Premathunga | Associate Technical Lead | WSO2 Inc. >> (m) +94711822074 | (w) +94112145345 | Email: ruks...@wso2.com >> GET INTEGRATION AGILE >> Integration Agility for Digitally Driven Business >> > > > -- > Thilini Shanika > Associate Technical Lead > WSO2, Inc.; http://wso2.com > 20, Palmgrove Avenue, Colombo 3 > > > -- Rukshan C. Premathunga | Associate Technical Lead | WSO2 Inc. (m) +94711822074 | (w) +94112145345 | Email: ruks...@wso2.com GET INTEGRATION AGILE Integration Agility for Digitally Driven Business
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
