fix: resolve API alias paths correctly for config files located outside the root folder #1823
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What/Why/How?
A bunch of fixes for problems I discovered while investigating other issues.
E.g., suppose we have this config file:
<starting-folder>/nested/redocly.yaml
:When running
redocly bundle --config nested/redocly.yaml alias@v1
, it would search for<starting-folder>/openapi.yaml
instead of<starting-folder>/nested/openapi.yaml
.(See the related snapshot).
The related changes are scoped to packages/cli/src/utils/miscellaneous.ts
Reference
Resolves #1351
Testing
Tested internally: https://github.com/Redocly/redocly/pull/12496
Screenshots (optional)
Check yourself
Security