Postman:请求时,请求不匹配架构
我正在使用Postman遵循OpenAPI 3和YAML格式的API,同时尝试验证我的API时遇到了错误。
即使我摆脱了正在处理的所有端点,我也无法验证API集合……它会影响以前创建的端点我尚未修改的端点。
即使我确认更改,我仍然会收到一条黄色的消息,说我没有解决问题,而且我又有了此屏幕再说一次。
I'm designing an API following the openAPI 3 and yaml format using Postman and I am running into a bug while trying to validate my API.
I can't validate the API collection even if I get rid of all the endpoints I am working on... And it affects previously created endpoints that I have not modified.
Even if I confirm the changes, I'll still get a yellow message saying that I have unresolved issues and I'm getting this screen again and again.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
解决方案/我如何修复它
您必须返回定义, delete 诉讼端点,然后 verative 和 sync 集合。验证后,您应该在下面的右上方获得绿色的“无问题”消息:
一旦您拥有这,您可以回到定义和添加先前已删除的诉讼端点。再次检查问题,您应该遇到问题,因为您正在添加“新”端点,只需确认更改即可。现在,您应该收到与右上角相同的绿色消息。问题是解决的。
Solution / How I fixed it
You must go back to the definition and delete the litigious endpoints and then validate and sync the collection. Once it's validated, you should get the green 'No issue found' message in the upper right like below:
Once you have this, you can go back to definition and add back the previously deleted litigious endpoints. Once again, check for issues, you should be getting issues because you're adding "new" endpoints, just confirm the changes. You should now be getting the same green message as before in the upper right corner. Issues are fixed.