-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
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
[BUG] Extractor does not work as expected for version-managed APIs #466
Comments
|
Please take a look at some open issues that address this topic. I know we are planning some changes in the upcoming versions. |
@waelkdouh |
@guythetechie thoughts on this one? |
please try v6 and let us know if it resolves your issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Release version
v4.10.2
Describe the bug
・Specification.yaml is incorrectly extracted for version-managed APIs (ex: v1/v2).
Even though the API should be extracted as v1 API , the contents of specification.yaml are overridden with v2 contents.
*In this case, the v2 API will be successfully extracted. Also, in any case, "files under operations" and "apiInformation.json" are successfully extracted.
・In some cases, v2 is extracted as v1.The main problems remain the same as described above.
・Completely random as to which API are incorrectly extracted.
Expected behavior
・specification.yaml will be extracted correctly.
*Can be extract without any difference from the version on Azure Portal
Actual behavior
description in "Describe the bug"
Reproduction Steps
・Create API by importing from Azure Portal instead of using Publisher.
・Run Extractor several times and compare the differences.
・This bug is reproduced randomly.
The text was updated successfully, but these errors were encountered: