-
-
Notifications
You must be signed in to change notification settings - Fork 284
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] Swagger issue on loading an undefined resource #2695
Comments
It seems to be coming from the validator badge |
Hello @VictoriqueMoe I finally decided to use the getAbsolutePath from It should solve your issue ;) |
🎉 This issue has been resolved in version 7.68.6 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
unfortantly, this did not solve the issue, i still get these 404's and the validator badge still errors i deployed the latest tsed and you can see the error here: https://waifuvault.moe/api-docs/ |
Ok. But now the path is directly get from swagger-ui-dist. So it's not related to the latest changes. Maybe the problem is related to swagger-ui-dist itself? |
But we can see a undefined string in the url. I'll check if other changes have introduce this regression. It's a bit complicated to repro in local when the badge is only displayed on a non localhost domain. I'll keep you informed if I found something ;) |
yeh, it's annoying for sure that is hard to test. editing the hosts file to proxy a localhost domain worked for me. also, no problem! it's not really a blocker. However, this is a blocker: https://github.com/orgs/tsedio/discussions/2697 if that counts for anything :D thank you as always for your amazing support and help |
Ho shit missed this issue. I'll try to find a way to fix that ASAP @VictoriqueMoe ;) |
Describe the bug
When i load Swagger (in Linux). i am getting some 404's on my network tab, these seem to be some sort of resource generated from an undefined.
see https://waifuvault.moe/api-docs/
Oddly enough, on my pc (Windows). when i load swagger, i don't get this, but also, i don't get the "valid" tick at the bottom right either. so not sure why it only happens when deployed on my production server
To Reproduce
Expected behavior
Loads swagger page with no errors
Code snippets
No response
Repository URL example
No response
OS
Ubuntu 23.10
Node version
v20.11.1
Library version
7.68.5
Additional context
No response
The text was updated successfully, but these errors were encountered: