Skip to content
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

apidom-ls inconsistency of codes #2109

Closed
tim-lai opened this issue Oct 6, 2022 · 1 comment · Fixed by #2112
Closed

apidom-ls inconsistency of codes #2109

tim-lai opened this issue Oct 6, 2022 · 1 comment · Fixed by #2112
Assignees
Labels
ApiDOM bug Something isn't working OpenApi 3.0

Comments

@tim-lai
Copy link
Contributor

tim-lai commented Oct 6, 2022

Q&A (please complete the following information)

  • ApiDOM version: 0.48.0

Describe the bug you're encountering

apidom-ls codes.ts
The following is a bug, where OPENAPI3_0_INFO_FIELD_VERSION_TYPE is given the same code grouping as OPENAPI3_0_OPEN_API_FIELD instead of with other OPENAPI3_0_INFO_FIELD(s)?

OPENAPI3_0_OPEN_API_FIELD_EXTERNAL_DOCS_TYPE = 5010700,
OPENAPI3_0_INFO_FIELD_VERSION_TYPE = 5010800,
OPENAPI3_0_INFO_FIELD_VERSION_REQUIRED,

OPENAPI3_0_INFO = 5020000,

vs should be

OPENAPI3_0_OPEN_API_FIELD_EXTERNAL_DOCS_TYPE = 5010700,

OPENAPI3_0_INFO = 5020000,
OPENAPI3_0_INFO_FIELD_VERSION_TYPE = 5020600,
OPENAPI3_0_INFO_FIELD_VERSION_REQUIRED,

Ref: PR 2106, in this comment

@tim-lai tim-lai self-assigned this Oct 6, 2022
@char0n char0n self-assigned this Oct 7, 2022
@char0n char0n added bug Something isn't working ApiDOM OpenApi 3.0 labels Oct 7, 2022
@char0n
Copy link
Member

char0n commented Oct 7, 2022

I'm processing this issue as I need to push forward with OpenAPI 3.0.x rules. THanks for reporting.

char0n added a commit that referenced this issue Oct 7, 2022
char0n added a commit that referenced this issue Oct 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ApiDOM bug Something isn't working OpenApi 3.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants