+1 for releasing 0.2.0.
We could get some feedback from community with this new release.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Mon, Nov 18, 2019 at 11:29 AM Daniel Qian wrote:
>
> The reasons why I suggest drop the Swagger 2.0 support are:
>
> 1. Some functions such as "contract
The reasons why I suggest drop the Swagger 2.0 support are:
1. Some functions such as "contract compatibility checking" and
"contract style checking" doesn't support Swagger 2.0, so that's weird
we support Swagger 2.0 in some functions while don't support in other
functions.
2. OpenAPI 3.0 growing
This road map is very excellent. I agree with the above development route.
But for the "Scaffold code generation" feature, maybe we can keep the
compatibility with swagger2.0?
There are a lot of features to be implemented.
What features do we want to include in the next release (0.2.0)?
Daniel Qia
Hi toolkit team,
We had a short talk on wechat about what should we do next on Toolkit
project. I think before we start we should have a discussion about the
roadmap, because Toolkit is a project composed by different functions.
Below are the main functions I can think of, and features can be
cat
