-
-
Notifications
You must be signed in to change notification settings - Fork 53
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
Prepare v2 #178
Prepare v2 #178
Conversation
@bastien-phi aside from updating docs, what else are you and @hotmeteor desiring for v2? |
I think @bastien-phi has knocked out almost every single issue, which is amazing. I'm going to chip away at some docs cleanup this morning. I don't think it needs to be enormous, but maybe just ensure it's clear what exactly this package handles, OpenAPI versioning, etc. |
I think it's possible to fix #140 before v2 but I did not have a lot of time recently because of client work. I think I will get some time next week to push a couple of PRs. This would make v2 almost ready. |
@bastien-phi Right on I've updated the README in this branch a little. If you have a minute, can you drop in this thread:
Basically anything you can think of that _might_be counter to what the docs did say. I can take it from there, but you are much closer to all the nuances of the changes. |
@hotmeteor I think I already covered everything in the upgrade guide. I'll take a look on that but everything should be up-to-date |
@hotmeteor I may be wrong but |
I think we are close from V2. @jarrodparkes can you take a look on this ? Merging this will pre-release the V2 thanks to the composer alias. @hotmeteor I will let you hit the release button when you want ! |
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. I made a small change for a typo I noticed
Thanks @jarrodparkes ! |
Adds a composer alias for v2 and upgrade guide.
It might need to be completed