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

--prefix-components-with-info-prop repeats prefixes multiple times in $ref's randomly #1287

Closed
Tracked by #1354
okamiraner opened this issue Oct 5, 2023 · 4 comments · Fixed by #1400
Closed
Tracked by #1354
Assignees
Labels
p3 Type: Bug Something isn't working

Comments

@okamiraner
Copy link

okamiraner commented Oct 5, 2023

When join multiple specification with the join command and the --prefix-components-with-info-prop flag, the resulting specification will contain references with prefixes repeated multiple times based of a random principle like that:

... $ref: '#/components/schemas/prefix_prefix_Component'

These references cannot be resolved later because components themselves prefixed one time as expected like that:

...
        prefix_Component:
...
@okamiraner okamiraner added the Type: Bug Something isn't working label Oct 5, 2023
@jeremyfiel
Copy link
Contributor

can you provide a minimal example?

@okamiraner
Copy link
Author

okamiraner commented Oct 7, 2023

Yes. Joining redoc.yaml and swagger.yaml gives a duplicate at line 428 in the resulting openapi.yaml if run:

$ redocly join redoc.yaml swagger.yaml --prefix-components-with-info-prop version --prefix-tags-with-filename

Archive.zip

@tatomyr tatomyr added the p3 label Oct 13, 2023
@tatomyr
Copy link
Contributor

tatomyr commented Oct 13, 2023

Thanks for reporting!
@IgorKarpiuk could you check if this is related to #1291 and the corresponding issue?

@IgorKarpiuk
Copy link
Contributor

@tatomyr It is not related

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p3 Type: Bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants