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
当前 apipark版本:v1.4.1-beta-2025-01-14T10:32:10Z,存在创建服务时,提示method(GET),path(/algorithm/*) is exist,异常,测试发现是。创建服务时默认创建一个:API 调用前缀 对应的api接口,导致创建服务时如果是相关的api调用前缀就会存在异常?这个是新增的服务添加逻辑(添加时api调用前缀值不能相同),还是隐藏的bug呢?
No response
uname -a
The text was updated successfully, but these errors were encountered:
不是bug哈,应该是你服务前缀重复了
Sorry, something went wrong.
这个,添加一个服务时,默认创建一个api,是正常的吗?
是正常的,设计如此
@ylcphantom 你好,我是apipark的产品经理,你是否有空做一下访谈? 想了解一下你目前的使用场景和对新功能的期望。随时可以加我微信:jeak01
No branches or pull requests
Current Behavior
当前 apipark版本:v1.4.1-beta-2025-01-14T10:32:10Z,存在创建服务时,提示method(GET),path(/algorithm/*) is exist,异常,测试发现是。创建服务时默认创建一个:API 调用前缀 对应的api接口,导致创建服务时如果是相关的api调用前缀就会存在异常?这个是新增的服务添加逻辑(添加时api调用前缀值不能相同),还是隐藏的bug呢?

Expected Behavior
No response
Error Logs
Steps to Reproduce
No response
Environment
uname -a
):The text was updated successfully, but these errors were encountered: