Repository navigation
[ISSUE #7593] Restore persisted api document menus and detail. - #7601
Closed
yangjj-iso wants to merge 1 commit into
Closed
yangjj-iso wants to merge 1 commit into
yangjj-iso wants to merge 1 commit into
Conversation
2 of 3 tasks
This file contains hidden or 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
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.
Superseded by #7603. This PR is the alternative repair approach and is closed to avoid reintroducing the legacy viewer endpoints removed there.
The selected removal approach retains database-backed API/tag management, existing API details, Swagger import, MCP generation and request debugging. Issue #7593 is addressed through its documented removal option by #7603; this repair branch is retained for reference.
Original repair proposal
Restore
GET /apidoc/getDocItem?id=...and read the document viewer's menu and detail from the persistedapi.documentdata. The menu previously used an unwritten in-memory map and the detail endpoint was missing.Menu leaves now contain database API ids, which the detail endpoint uses to return the stored
DocItem. Group persisted Swagger documents by context path and module, preserve module/API ordering, and skip malformed or incompatible records. Updates and deletions are visible on the next read without requiring re-import. The viewer consumes legacyDocItemdocuments; OpenAPI-operation payloads remain available through the existing/api/{id}detail route.Validation:
shenyu-adminApache RAT check passed../mvnw -pl shenyu-admin -am test -Dtest=ApiDocControllerTest,DocManagerImplTest,ApiMapperTest,SwaggerImportServiceTest,SwaggerImportServiceImplTest,SwaggerDocParserTest -Dsurefire.failIfNoSpecifiedTests=false -Dmaven.javadoc.skip=true -Djacoco.skip=true -Drat.skip=true ./mvnw -pl shenyu-admin apache-rat:check./mvnw clean install -Dmaven.javadoc.skip=true(targeted validation above).