-
Notifications
You must be signed in to change notification settings - Fork 42
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
[backbport v4.x] fix: html urls should not be absolute #179
[backbport v4.x] fix: html urls should not be absolute #179
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
@DavidTanner looks like CI is failing for |
@dancastillo when was the last time the build passed for this branch? I saw other PRs that were merged with the same failures. I can check tomorrow |
Good callout, looks like this has been failing for a while now https://github.com/fastify/fastify-swagger-ui/commits/v4.x/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@dancastillo can you make a PR removing the package manager ci? |
Oh never mind it's a backport |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Checklist
npm run test
andnpm run benchmark
and the Code of conduct
When the HTML uses an absolute URL,
/documentation/index.css
, then the browser requests the data from the/
. This is an issue if swagger is set up as a nested route. I added a test for this where swagger is registered as a child of another prefix route.Fixed #176
Related to #164, #162