Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When integrating smart-doc in a Dubbo Provider, it results in the generation of duplicated interface documents. #531

Closed
Fioooooooo opened this issue Jun 26, 2023 · 1 comment
Labels
bug Something isn't working
Milestone

Comments

@Fioooooooo
Copy link
Contributor

Fioooooooo commented Jun 26, 2023

Your Environment (Your Usage Environment)

  • smart-doc version: 2.7.1

Problem Description

When generating RPC interface documentation, smart-doc includes non-default methods from parent interfaces directly into the methodDocList to ensure inherited methods are scanned. This approach works appropriately in a Dubbo API module integrated with smart-doc, as it is necessary to retrieve all methods within the interface.

However, this leads to an issue when integrating smart-doc in a Dubbo Provider: both the implementation class's methods and those of its interface are entirely scanned, resulting in duplicate generation of interface documentation.

image

Affected Versions

smart-doc versions from [2.6.9 to 2.7.1] are impacted by this issue.

@Fioooooooo Fioooooooo added the bug Something isn't working label Jun 26, 2023
@shalousun
Copy link
Collaborator

good

shalousun added a commit that referenced this issue Jun 27, 2023
fix #531 修复 rpc 文档重复生成
@shalousun shalousun added this to the 2.7.2 milestone Jul 2, 2023
@shalousun shalousun changed the title 在 dubbo provider 集成 smart-doc,会生成重复的接口 When integrating smart-doc in a Dubbo Provider, it results in the generation of duplicated interface documents. May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants