-
Notifications
You must be signed in to change notification settings - Fork 483
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
Fix: doc versioning by header #2063
Conversation
package.json
Outdated
@@ -40,7 +40,7 @@ | |||
"@nestjs/platform-fastify": "9.0.11", | |||
"@types/jest": "28.1.7", | |||
"@types/js-yaml": "4.0.5", | |||
"@types/lodash": "4.14.182", | |||
"@types/lodash": "4.14.184", |
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.
why do we need to upgrade this? 🤔
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.
It's already updated on master, it's a fail from my rebase: 67c78e4
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.
coud you rebase it again? looks like we got some conflicts to fix
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.
Sure, it's done
Apologies for not reviewing this sooner! Could you please resolve conflicts? Also, any chance we can add an e2e test too (with enabled versioning by header)? |
Any updates on this? Looking forward to being able to use it! :) |
is there anything remaining to merge this? happy to contribute to this PR to get it merged |
We're still waiting for e2e tests to be added |
Any news on this? |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: 1495
What is the new behavior?
Versioning documentation is now working for header versioning.
Does this PR introduce a breaking change?
Other information