Hi all,
It's a pleasure to join the Apache ServiceComb community
In the last few months, I got a lot of help in the community and thanks
for everyone's help.
I love open source and hope to push ServiceComb ahead with you
Yours,
Lisen Sun
Daniel Qian 于2019年12月23日周一 下午3:41写道：
>
Congrats!
Bin Ma 于2019年12月23日周一 下午2:32写道：
>
> Please join me and the rest of the ServiceComb PMC members in welcoming our
> new ServiceComb committer: Sun Lisen(孙丽森).
>
> Sun Lisen has been around the ServiceComb almost a year by
> contributing patches for servicecomb-toolkit,
>
Please join me and the rest of the ServiceComb PMC members in welcoming our
new ServiceComb committer: Sun Lisen(孙丽森).
Sun Lisen has been around the ServiceComb almost a year by
contributing patches for servicecomb-toolkit,
servicecomb-java-chassis,servicecomb-website and
discussion techniques
Hi Willem,
I mean OpenAPI yaml written by hand. And yes, we need to track all
the change by means of git.
And large Swagger often needs to be maintained by several people, and
that's the conflict happens.
OpenAPI v3 provide Components[1] to reuse Schema, Response, Request,
etc. But that's no
Hi Daniel
Could you explain more about it?
If the Swagger yaml is generated from the code, it's make sense that
we don't put this yaml files into VCS.
But if we write the Swagger yaml file by hand, I think we need to keep
the track of all the changes.
Willem Jiang
Twitter: willemjiang
Weibo:
Hi toolkit guys,
OpenAPI/Swagger yaml is a good standard to describe the APIs, but it's
easy to get hundreds, even thousands lines in the file. That becomes
hard to maintain and easy to get into the VCS conflict situation.
How do you guys solve this problem in real development? I've heard
that
