8000 [PhpUnitBridge] Add keyword `dev` to leverage composer hint by OskarStark · Pull Request #51925 · symfony/symfony · GitHub
[go: up one dir, main page]

Skip to content

[PhpUnitBridge] Add keyword dev to leverage composer hint #51925

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

Merged
merged 1 commit into from
Oct 10, 2023

Conversation

OskarStark
Copy link
Contributor
Q A
Branch? 5.4
Bug fix? no
New feature? no
Deprecations? no
Tickets -
License MIT

@OskarStark OskarStark self-assigned this Oct 10, 2023
@carsonbot carsonbot added this to the 5.4 milestone Oct 10, 2023
@OskarStark OskarStark requested a review from stof October 10, 2023 06:20
@carsonbot carsonbot changed the title Add keyword dev to leverage composer hint [PhpUnitBridge] Add keyword dev to leverage composer hint Oct 10, 2023
@fabpot
Copy link
Member
fabpot commented Oct 10, 2023

Thank you @OskarStark.

@fabpot fabpot merged commit 00adb85 into symfony:5.4 Oct 10, 2023
@@ -2,7 +2,7 @@
"name": "symfony/phpunit-bridge",
"type": "symfony-bridge",
"description": "Provides utilities for PHPUnit, especially user deprecation notices management",
"keywords": [],
"keywords": ['dev'],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are single quotes valid json?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, but @fabpot fixed it while merging in e86d26a

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not yet :)
I fixed it just after the merge when I realized that ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
0