Skip to content
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

Merge 10.1.x up into 11.0.x #303

Merged
merged 14 commits into from
Dec 11, 2022
Merged

Merge 10.1.x up into 11.0.x #303

merged 14 commits into from
Dec 11, 2022

Conversation

greg0ire
Copy link
Member

@greg0ire greg0ire commented Dec 10, 2022

I'm going to have to adjust tests, by first making them fail instead of crashing on patch

UPDATE: Done.

greg0ire and others added 13 commits August 26, 2022 14:11
People will be more likely to read this guide.
As per https://getcomposer.org/doc/04-schema.md#keywords by including
"dev" as a keyword in the `composer.json` file, Composer 2.4.0-RC1 and
later will prompt users if the package is installed with `composer
require` instead of `composer require --dev`. See
composer/composer#10960 for more info.
Upstream package has fixed a false positive with self::CONSTANT

Here is how the false positive looked like

>   9 | ERROR | [ ] Invalid inline documentation comment format "@var int", expected "@var type $variable Optional description".
>     |       |     (SlevomatCodingStandard.Commenting.InlineDocCommentDeclaration.InvalidFormat)

It was about these lines:

> /** @var int */
> const FOO = 123;
@greg0ire greg0ire marked this pull request as ready for review December 10, 2022 12:19
@greg0ire greg0ire requested a review from a team December 10, 2022 12:19
@greg0ire greg0ire mentioned this pull request Dec 10, 2022
@ostrolucky ostrolucky merged commit 8c3c932 into doctrine:11.0.x Dec 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants