+1. OAS 2,0 to 3.0.0 conversion is straight forward. While working on OAS code generator i found even if we provided 2.0.0 definition it internally convert to 3.0.0 and then perform all logic on 3.0.0 code. I think that part happens in core component. So making 3.0.0 internally will not be issue at all.
Thanks, sanjeewa. On Mon, Aug 12, 2019 at 11:36 AM Thilini Shanika <thili...@wso2.com> wrote: > We can set OAS 3.0 as the version supported by default, but let's keep the > advanced option to create new APIs in OAS 2.0 as well. > > On Mon, Aug 12, 2019 at 11:23 AM Pubudu Gunatilaka <pubu...@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? >>> >> +1 to go with v3 as we are releasing a major version for APIM. >> >>> >> Thank you! >> -- >> *Pubudu Gunatilaka* | Associate Technical Lead | WSO2 Inc. >> (m) +94774078049 | (w) +94112145345 | (e) pubu...@wso2.com >> <http://wso2.com/signature> >> >> > > -- > Thilini Shanika > Associate Technical Lead > WSO2, Inc.; http://wso2.com > 20, Palmgrove Avenue, Colombo 3 > > > -- *Sanjeewa Malalgoda* Software Architect | Associate Director, Engineering - WSO2 Inc. (m) +94 712933253 | (e) sanje...@wso2.com | (b) Blogger <http://sanjeewamalalgoda.blogspot.com>, Medium <https://medium.com/@sanjeewa190> GET INTEGRATION AGILE <https://wso2.com/signature> Integration Agility for Digitally Driven Business
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
