Aias00 opened a new issue, #7594:
URL: https://github.com/apache/shenyu/issues/7594
## Symptom
`ApiSourceEnum` defines `IMPORT_YAPI("import_yapi", 4)`
(`shenyu-common/.../enums/ApiSourceEnum.java:48`), and the admin UI offers an
"import yapi" choice, but there is **no backend implementation** of YAPI import
anywhere in the codebase (no `YapiImport*`, no `YapiDoc*`, no
`YapiImportService`/`Controller`). Selecting the YAPI source leads nowhere.
## Evidence
- Repo-wide search for `yapi` (case-insensitive, excluding unrelated
`ProxyApiKey` / `queryByApiId` substring hits) returns only the enum constant
and a doc comment in `ApiDTO` ("4-import yapi"); no import logic.
- `ApiSourceEnum.IMPORT_YAPI` is never read by any import branch (the only
import branches are swagger import / annotation generation).
## Impact
A documented / UI-exposed capability is non-functional; users may configure
an import source that silently does nothing.
## Options
- **Implement** YAPI import: fetch the YAPI project JSON, map it to
`ApiDocRegisterDTO` / `MetaDataRegisterDTO` (reuse `SwaggerDocParser` or add a
new `YapiDocParser`).
- **Or remove** `IMPORT_YAPI` and the UI option to avoid advertising an
unimplemented feature.
## Related
- #7592 (dead `DOC_DEFINITION_MAP` / apidoc viewer removal, same API-doc
area).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
