-
-
Notifications
You must be signed in to change notification settings - Fork 843
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
chore: allow zircote/swagger-php v5 #2420
Conversation
Ready for review! 😄 |
9a7295c
to
281bc89
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2420 +/- ##
==========================================
- Coverage 89.56% 89.56% -0.01%
==========================================
Files 78 79 +1
Lines 2914 2912 -2
==========================================
- Hits 2610 2608 -2
Misses 304 304 ☔ View full report in Codecov by Sentry. |
1bc3b7b
to
701ab46
Compare
Looking at the code coverage report: I do not think that the Because of the string before support I needed to upgrade the minimum to 4.11.1, because otherwise more code from zircote would needed to be integrated here. |
701ab46
to
1718b21
Compare
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.
Thank you! ❤️
Description
zircote/swagger-php v5 has been released, and seems to only require minimal updates. See https://github.com/zircote/swagger-php/blob/master/docs/guide/migrating-to-v5.md.
I did need to migrate the current processor implementation to the one that is using the new processor pipeline introduced with 4.10.0, which is why I bumped the minimum constraint. In order to not mess up dependency injection, I was required to wrap the Generator class in order to allow adding additional processors using the existing compiler pass.
What type of PR is this? (check all applicable)
Checklist
docs/
)CHANGELOG.md
)