We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
当前的参数属性“IConfigFromPluginsJoi”只有部分“@umijs/openapi”属性可进行配置,期望将GenerateServiceProps的参数都能透传到config.ts的openAPI中配置 需求背景:
目前执行npm run openapi后的目录现状
npm run openapi
|-mock | |-currentUser.mock.ts | |-getFakeCaptcha.mock.ts | |-src | |-service | |- projectName | |- api.ts | |- login.ts | |- index.ts | |- typings.d.ts
可以看出,mock文件是按operationId命名的,相当于一个方法一个文件,且没有放到projectName下,这对于一个系统好几百个接口,就有问题了,不好排查,service文件是按照tags做了分组,一个项目的在一个目录下,对于微服务架构的后台,这种方式是可以的,但对于单体服务,就不太合适了,所以希望这里能再灵活一些。
期望效果
The text was updated successfully, but these errors were encountered:
No branches or pull requests
当前的参数属性“IConfigFromPluginsJoi”只有部分“@umijs/openapi”属性可进行配置,期望将GenerateServiceProps的参数都能透传到config.ts的openAPI中配置
需求背景:
目前执行
npm run openapi
后的目录现状可以看出,mock文件是按operationId命名的,相当于一个方法一个文件,且没有放到projectName下,这对于一个系统好几百个接口,就有问题了,不好排查,service文件是按照tags做了分组,一个项目的在一个目录下,对于微服务架构的后台,这种方式是可以的,但对于单体服务,就不太合适了,所以希望这里能再灵活一些。
期望效果
The text was updated successfully, but these errors were encountered: