Compatible with native Swagger Tag content. #670
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Are you not using the 3.0 protocol, but rather the Swagger2 protocol? Does the open API of 3.0 also need to be fixed? |
|
Let's rebase it and keep only one effective message. If it's convenient, you can also help us register. |
|
shalousun
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The native Swagger's tag information includes details such as the controller class and methods, allowing the front end to automatically generate code based on the tag information. The tag information in smart-doc only contains interface descriptions, which cannot be utilized by front-end frameworks.
原生的Swagger的tag信息会包含controller类和方发等信息，前端可以根据tag信息自动生成前端代码。smart-doc的tag信息只有接口描述，前端框架无法使用，