-
-
Notifications
You must be signed in to change notification settings - Fork 933
Get back return phpdoc on ProviderInterface #5253
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
Closed
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merge 3.0 onto main
Merge 3.0 into main
* fix: update yaml extractor test file coding standard (api-platform#5068) * fix(graphql): add clearer error message when TwigBundle is disabled but graphQL clients are enabled (api-platform#5064) * fix(metadata): add class key in payload argument resolver (api-platform#5067) * fix: add class key in payload argument resolver * add null if everything else goes wrong * fix: upgrade command remove ApiSubresource attribute (api-platform#5049) Fixes api-platform#5038 * fix(doctrine): use abitrary index instead of value (api-platform#5079) * fix: uri template should respect rfc 6570 (api-platform#5080) * fix: remove @internal annotation for Operations (api-platform#5089) See api-platform#5084 * fix(metadata): define a name on a single operation (api-platform#5090) fixes api-platform#5082 * fix(metadata): deprecate when user decorates in legacy mode (api-platform#5091) fixes api-platform#5078 * fix(graphql): use right nested operation (api-platform#5102) * Revert "fix(graphql): use right nested operation (api-platform#5102)" (api-platform#5111) This reverts commit 44337dd. * fix(graphql): always allow to query nested resources (api-platform#5112) * fix(graphql): always allow to query nested resources * review Co-authored-by: Alan Poulain <contact@alanpoulain.eu> * chore: php-cs-fixer update * fix: only alias if exists for opcache preload Fixes api-platform/api-platform#2284 (api-platform#5110) Co-authored-by: Liviu Mirea <liviu.mirea@wecodepixels.com> * chore: php-cs-fixer update (api-platform#5118) * chore: php-cs-fixer update * chore: php-cs-fixer update * fix(metadata): upgrade script keep operation name (api-platform#5109) origin: api-platform#5105 Co-authored-by: WilliamPeralta <william.peralta18@gmail.com> * chore: v2.7.3 changelog * chore: v3.0.3 changelog Co-authored-by: helyakin <CourcierMarvin@gmail.com> Co-authored-by: ArnoudThibaut <thibaut.arnoud@gmail.com> Co-authored-by: davy-beauzil <38990335+davy-beauzil@users.noreply.github.com> Co-authored-by: Baptiste Leduc <baptiste.leduc@gmail.com> Co-authored-by: Xavier Laviron <norival@users.noreply.github.com> Co-authored-by: Alan Poulain <contact@alanpoulain.eu> Co-authored-by: Liviu Cristian Mirea-Ghiban <contact@liviucmg.com> Co-authored-by: Liviu Mirea <liviu.mirea@wecodepixels.com> Co-authored-by: WilliamPeralta <william.peralta18@gmail.com>
This reverts commit 6abd0fe.
chore: squashed a merge this is why you don't do this friday
* ci: use stable version of auto-release * ci: remove tagged-release * chore: use a stale label instead of wontfix
PHPStan PHPDoc-Parser is used instead of phpDocumentor because the latter is not actively maintained anymore.
* fix(openapi): resource classes are no longer considered as enum * feat: make property metadata factories work with enum cases * feat: add GraphQL enum support
please change your commit message to follow conventional commits |
During migration from 2.7 to 3.0 I noticed we lost this very useful return
thanks 55be4ca |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During migration from 2.7 to 3.0 I noticed we lost this very useful return