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-reference: URL resolution doesn't understand combination of special character in URL #3923

Closed
char0n opened this issue Mar 13, 2024 · 2 comments
Assignees
Labels
ApiDOM bug Something isn't working

Comments

@char0n
Copy link
Member

char0n commented Mar 13, 2024

Example URL: https://api.sap.com/odata/1.0/catalog.svc/APIContent.APIs('SAP_ICSM_StudyService')/$value?type=json

apidom-reference will reject to resolve/deference/parse the URL.

@char0n char0n added bug Something isn't working ApiDOM labels Mar 13, 2024
@char0n
Copy link
Member Author

char0n commented Aug 15, 2024

This issue has been caused by file extension issue described in #4298. As URL mentioned in this issue don't have file extension, parser plugins failed to parse it. After fixing #4298, this issue no longer manifests.

@rainum
Copy link
Contributor

rainum commented Aug 15, 2024

Thanks for the update, @char0n! Here are a couple of other thoughts from my side.

Playground failed to process the example URL due to the CORS error:

image

When I recreated the same complex path in my personal repo, it worked just fine:

complex_path.mp4

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
Projects
None yet
Development

No branches or pull requests

2 participants