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

feat: set new_with_parentheses for anonymous_class to false in PER-CS2.0 #8140

Merged
merged 4 commits into from
Aug 7, 2024
Merged

feat: set new_with_parentheses for anonymous_class to false in PER-CS2.0 #8140

merged 4 commits into from
Aug 7, 2024

Conversation

bonroyage
Copy link
Contributor

The spec for PER CS 2.0 states in chapter 8 that anonymous classes without arguments must not have parentheses:

If the anonymous class has no arguments, the () after class MUST be omitted. For example:

<?php

// Brace on the same line
// No arguments
$instance = new class extends \Foo implements \HandleableInterface {
    // Class content
};

The inheritance from PSR12 currently sets the new_with_parentheses to true for both named and anonymous classes

'new_with_parentheses' => true,

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
@coveralls
Copy link

coveralls commented Jul 25, 2024

Coverage Status

coverage: 95.161%. remained the same
when pulling e145777 on bonroyage:new_with_parentheses
into ed86702 on PHP-CS-Fixer:master.

@bonroyage bonroyage changed the title Set new_with_parentheses for anonymous_class to false in PER-CS2.0 fix: Set new_with_parentheses for anonymous_class to false in PER-CS2.0 Jul 25, 2024
@keradus
Copy link
Member

keradus commented Jul 31, 2024

side note:
we classify this as feature, not bugfix
ref https://github.com/PHP-CS-Fixer/PHP-CS-Fixer/blob/master/feature-or-bug.rst#feature

@keradus keradus changed the title fix: Set new_with_parentheses for anonymous_class to false in PER-CS2.0 feat: set new_with_parentheses for anonymous_class to false in PER-CS2.0 Jul 31, 2024
derrabus added a commit to symfony/symfony that referenced this pull request Aug 6, 2024
…`` (parentheses for anonymous classes) (bonroyage)

This PR was squashed before being merged into the 7.2 branch.

Discussion
----------

Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)

| Q             | A
| ------------- | ---
| Branch?       | 7.2
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

I have created a PR (PHP-CS-Fixer/PHP-CS-Fixer#8140) in the PHP-CS-Fixer repo to bring the ``@PER`-CS2.0` ruleset in line with the specifications on the `new_with_parentheses` rule for anonymous classes. Since the ``@Symfony`` ruleset builds upon the ``@PER`-CS2.0` ruleset, they would like confirmation that the Symfony community is OK with this change affecting the Symfony ruleset as well. Should it not be, I'll push another commit there ensuring that the change does not affect ``@Symfony``.

Therefore, this PR is not meant to be merged, but function as an RFC to get your opinion and show the effect it would have when applied to the Symfony source.

Commits
-------

506e0dd Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)
symfony-splitter pushed a commit to symfony/mailer that referenced this pull request Aug 6, 2024
…`` (parentheses for anonymous classes) (bonroyage)

This PR was squashed before being merged into the 7.2 branch.

Discussion
----------

Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)

| Q             | A
| ------------- | ---
| Branch?       | 7.2
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

I have created a PR (PHP-CS-Fixer/PHP-CS-Fixer#8140) in the PHP-CS-Fixer repo to bring the ``@PER`-CS2.0` ruleset in line with the specifications on the `new_with_parentheses` rule for anonymous classes. Since the ``@Symfony`` ruleset builds upon the ``@PER`-CS2.0` ruleset, they would like confirmation that the Symfony community is OK with this change affecting the Symfony ruleset as well. Should it not be, I'll push another commit there ensuring that the change does not affect ``@Symfony``.

Therefore, this PR is not meant to be merged, but function as an RFC to get your opinion and show the effect it would have when applied to the Symfony source.

Commits
-------

506e0dd327 Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)
symfony-splitter pushed a commit to symfony/validator that referenced this pull request Aug 6, 2024
…`` (parentheses for anonymous classes) (bonroyage)

This PR was squashed before being merged into the 7.2 branch.

Discussion
----------

Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)

| Q             | A
| ------------- | ---
| Branch?       | 7.2
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

I have created a PR (PHP-CS-Fixer/PHP-CS-Fixer#8140) in the PHP-CS-Fixer repo to bring the ``@PER`-CS2.0` ruleset in line with the specifications on the `new_with_parentheses` rule for anonymous classes. Since the ``@Symfony`` ruleset builds upon the ``@PER`-CS2.0` ruleset, they would like confirmation that the Symfony community is OK with this change affecting the Symfony ruleset as well. Should it not be, I'll push another commit there ensuring that the change does not affect ``@Symfony``.

Therefore, this PR is not meant to be merged, but function as an RFC to get your opinion and show the effect it would have when applied to the Symfony source.

Commits
-------

506e0dd327 Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)
symfony-splitter pushed a commit to symfony/doctrine-bridge that referenced this pull request Aug 6, 2024
…`` (parentheses for anonymous classes) (bonroyage)

This PR was squashed before being merged into the 7.2 branch.

Discussion
----------

Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)

| Q             | A
| ------------- | ---
| Branch?       | 7.2
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

I have created a PR (PHP-CS-Fixer/PHP-CS-Fixer#8140) in the PHP-CS-Fixer repo to bring the ``@PER`-CS2.0` ruleset in line with the specifications on the `new_with_parentheses` rule for anonymous classes. Since the ``@Symfony`` ruleset builds upon the ``@PER`-CS2.0` ruleset, they would like confirmation that the Symfony community is OK with this change affecting the Symfony ruleset as well. Should it not be, I'll push another commit there ensuring that the change does not affect ``@Symfony``.

Therefore, this PR is not meant to be merged, but function as an RFC to get your opinion and show the effect it would have when applied to the Symfony source.

Commits
-------

506e0dd327 Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)
symfony-splitter pushed a commit to symfony/twig-bridge that referenced this pull request Aug 6, 2024
…`` (parentheses for anonymous classes) (bonroyage)

This PR was squashed before being merged into the 7.2 branch.

Discussion
----------

Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)

| Q             | A
| ------------- | ---
| Branch?       | 7.2
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

I have created a PR (PHP-CS-Fixer/PHP-CS-Fixer#8140) in the PHP-CS-Fixer repo to bring the ``@PER`-CS2.0` ruleset in line with the specifications on the `new_with_parentheses` rule for anonymous classes. Since the ``@Symfony`` ruleset builds upon the ``@PER`-CS2.0` ruleset, they would like confirmation that the Symfony community is OK with this change affecting the Symfony ruleset as well. Should it not be, I'll push another commit there ensuring that the change does not affect ``@Symfony``.

Therefore, this PR is not meant to be merged, but function as an RFC to get your opinion and show the effect it would have when applied to the Symfony source.

Commits
-------

506e0dd327 Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)
symfony-splitter pushed a commit to symfony/serializer that referenced this pull request Aug 6, 2024
…`` (parentheses for anonymous classes) (bonroyage)

This PR was squashed before being merged into the 7.2 branch.

Discussion
----------

Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)

| Q             | A
| ------------- | ---
| Branch?       | 7.2
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

I have created a PR (PHP-CS-Fixer/PHP-CS-Fixer#8140) in the PHP-CS-Fixer repo to bring the ``@PER`-CS2.0` ruleset in line with the specifications on the `new_with_parentheses` rule for anonymous classes. Since the ``@Symfony`` ruleset builds upon the ``@PER`-CS2.0` ruleset, they would like confirmation that the Symfony community is OK with this change affecting the Symfony ruleset as well. Should it not be, I'll push another commit there ensuring that the change does not affect ``@Symfony``.

Therefore, this PR is not meant to be merged, but function as an RFC to get your opinion and show the effect it would have when applied to the Symfony source.

Commits
-------

506e0dd327 Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)
symfony-splitter pushed a commit to symfony/security-bundle that referenced this pull request Aug 6, 2024
…`` (parentheses for anonymous classes) (bonroyage)

This PR was squashed before being merged into the 7.2 branch.

Discussion
----------

Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)

| Q             | A
| ------------- | ---
| Branch?       | 7.2
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

I have created a PR (PHP-CS-Fixer/PHP-CS-Fixer#8140) in the PHP-CS-Fixer repo to bring the ``@PER`-CS2.0` ruleset in line with the specifications on the `new_with_parentheses` rule for anonymous classes. Since the ``@Symfony`` ruleset builds upon the ``@PER`-CS2.0` ruleset, they would like confirmation that the Symfony community is OK with this change affecting the Symfony ruleset as well. Should it not be, I'll push another commit there ensuring that the change does not affect ``@Symfony``.

Therefore, this PR is not meant to be merged, but function as an RFC to get your opinion and show the effect it would have when applied to the Symfony source.

Commits
-------

506e0dd327 Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)
symfony-splitter pushed a commit to symfony/http-foundation that referenced this pull request Aug 6, 2024
…`` (parentheses for anonymous classes) (bonroyage)

This PR was squashed before being merged into the 7.2 branch.

Discussion
----------

Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)

| Q             | A
| ------------- | ---
| Branch?       | 7.2
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

I have created a PR (PHP-CS-Fixer/PHP-CS-Fixer#8140) in the PHP-CS-Fixer repo to bring the ``@PER`-CS2.0` ruleset in line with the specifications on the `new_with_parentheses` rule for anonymous classes. Since the ``@Symfony`` ruleset builds upon the ``@PER`-CS2.0` ruleset, they would like confirmation that the Symfony community is OK with this change affecting the Symfony ruleset as well. Should it not be, I'll push another commit there ensuring that the change does not affect ``@Symfony``.

Therefore, this PR is not meant to be merged, but function as an RFC to get your opinion and show the effect it would have when applied to the Symfony source.

Commits
-------

506e0dd327 Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)
symfony-splitter pushed a commit to symfony/security-core that referenced this pull request Aug 6, 2024
…`` (parentheses for anonymous classes) (bonroyage)

This PR was squashed before being merged into the 7.2 branch.

Discussion
----------

Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)

| Q             | A
| ------------- | ---
| Branch?       | 7.2
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

I have created a PR (PHP-CS-Fixer/PHP-CS-Fixer#8140) in the PHP-CS-Fixer repo to bring the ``@PER`-CS2.0` ruleset in line with the specifications on the `new_with_parentheses` rule for anonymous classes. Since the ``@Symfony`` ruleset builds upon the ``@PER`-CS2.0` ruleset, they would like confirmation that the Symfony community is OK with this change affecting the Symfony ruleset as well. Should it not be, I'll push another commit there ensuring that the change does not affect ``@Symfony``.

Therefore, this PR is not meant to be merged, but function as an RFC to get your opinion and show the effect it would have when applied to the Symfony source.

Commits
-------

506e0dd327 Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)
symfony-splitter pushed a commit to symfony/contracts that referenced this pull request Aug 6, 2024
…`` (parentheses for anonymous classes) (bonroyage)

This PR was squashed before being merged into the 7.2 branch.

Discussion
----------

Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)

| Q             | A
| ------------- | ---
| Branch?       | 7.2
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

I have created a PR (PHP-CS-Fixer/PHP-CS-Fixer#8140) in the PHP-CS-Fixer repo to bring the ``@PER`-CS2.0` ruleset in line with the specifications on the `new_with_parentheses` rule for anonymous classes. Since the ``@Symfony`` ruleset builds upon the ``@PER`-CS2.0` ruleset, they would like confirmation that the Symfony community is OK with this change affecting the Symfony ruleset as well. Should it not be, I'll push another commit there ensuring that the change does not affect ``@Symfony``.

Therefore, this PR is not meant to be merged, but function as an RFC to get your opinion and show the effect it would have when applied to the Symfony source.

Commits
-------

506e0dd327 Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)
symfony-splitter pushed a commit to symfony/var-exporter that referenced this pull request Aug 6, 2024
…`` (parentheses for anonymous classes) (bonroyage)

This PR was squashed before being merged into the 7.2 branch.

Discussion
----------

Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)

| Q             | A
| ------------- | ---
| Branch?       | 7.2
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

I have created a PR (PHP-CS-Fixer/PHP-CS-Fixer#8140) in the PHP-CS-Fixer repo to bring the ``@PER`-CS2.0` ruleset in line with the specifications on the `new_with_parentheses` rule for anonymous classes. Since the ``@Symfony`` ruleset builds upon the ``@PER`-CS2.0` ruleset, they would like confirmation that the Symfony community is OK with this change affecting the Symfony ruleset as well. Should it not be, I'll push another commit there ensuring that the change does not affect ``@Symfony``.

Therefore, this PR is not meant to be merged, but function as an RFC to get your opinion and show the effect it would have when applied to the Symfony source.

Commits
-------

506e0dd327 Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)
symfony-splitter pushed a commit to symfony/dependency-injection that referenced this pull request Aug 6, 2024
…`` (parentheses for anonymous classes) (bonroyage)

This PR was squashed before being merged into the 7.2 branch.

Discussion
----------

Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)

| Q             | A
| ------------- | ---
| Branch?       | 7.2
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

I have created a PR (PHP-CS-Fixer/PHP-CS-Fixer#8140) in the PHP-CS-Fixer repo to bring the ``@PER`-CS2.0` ruleset in line with the specifications on the `new_with_parentheses` rule for anonymous classes. Since the ``@Symfony`` ruleset builds upon the ``@PER`-CS2.0` ruleset, they would like confirmation that the Symfony community is OK with this change affecting the Symfony ruleset as well. Should it not be, I'll push another commit there ensuring that the change does not affect ``@Symfony``.

Therefore, this PR is not meant to be merged, but function as an RFC to get your opinion and show the effect it would have when applied to the Symfony source.

Commits
-------

506e0dd327 Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)
symfony-splitter pushed a commit to symfony/mime that referenced this pull request Aug 6, 2024
…`` (parentheses for anonymous classes) (bonroyage)

This PR was squashed before being merged into the 7.2 branch.

Discussion
----------

Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)

| Q             | A
| ------------- | ---
| Branch?       | 7.2
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

I have created a PR (PHP-CS-Fixer/PHP-CS-Fixer#8140) in the PHP-CS-Fixer repo to bring the ``@PER`-CS2.0` ruleset in line with the specifications on the `new_with_parentheses` rule for anonymous classes. Since the ``@Symfony`` ruleset builds upon the ``@PER`-CS2.0` ruleset, they would like confirmation that the Symfony community is OK with this change affecting the Symfony ruleset as well. Should it not be, I'll push another commit there ensuring that the change does not affect ``@Symfony``.

Therefore, this PR is not meant to be merged, but function as an RFC to get your opinion and show the effect it would have when applied to the Symfony source.

Commits
-------

506e0dd327 Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)
symfony-splitter pushed a commit to symfony/console that referenced this pull request Aug 6, 2024
…`` (parentheses for anonymous classes) (bonroyage)

This PR was squashed before being merged into the 7.2 branch.

Discussion
----------

Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)

| Q             | A
| ------------- | ---
| Branch?       | 7.2
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

I have created a PR (PHP-CS-Fixer/PHP-CS-Fixer#8140) in the PHP-CS-Fixer repo to bring the ``@PER`-CS2.0` ruleset in line with the specifications on the `new_with_parentheses` rule for anonymous classes. Since the ``@Symfony`` ruleset builds upon the ``@PER`-CS2.0` ruleset, they would like confirmation that the Symfony community is OK with this change affecting the Symfony ruleset as well. Should it not be, I'll push another commit there ensuring that the change does not affect ``@Symfony``.

Therefore, this PR is not meant to be merged, but function as an RFC to get your opinion and show the effect it would have when applied to the Symfony source.

Commits
-------

506e0dd327 Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)
symfony-splitter pushed a commit to symfony/form that referenced this pull request Aug 6, 2024
…`` (parentheses for anonymous classes) (bonroyage)

This PR was squashed before being merged into the 7.2 branch.

Discussion
----------

Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)

| Q             | A
| ------------- | ---
| Branch?       | 7.2
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

I have created a PR (PHP-CS-Fixer/PHP-CS-Fixer#8140) in the PHP-CS-Fixer repo to bring the ``@PER`-CS2.0` ruleset in line with the specifications on the `new_with_parentheses` rule for anonymous classes. Since the ``@Symfony`` ruleset builds upon the ``@PER`-CS2.0` ruleset, they would like confirmation that the Symfony community is OK with this change affecting the Symfony ruleset as well. Should it not be, I'll push another commit there ensuring that the change does not affect ``@Symfony``.

Therefore, this PR is not meant to be merged, but function as an RFC to get your opinion and show the effect it would have when applied to the Symfony source.

Commits
-------

506e0dd327 Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)
symfony-splitter pushed a commit to symfony/messenger that referenced this pull request Aug 6, 2024
…`` (parentheses for anonymous classes) (bonroyage)

This PR was squashed before being merged into the 7.2 branch.

Discussion
----------

Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)

| Q             | A
| ------------- | ---
| Branch?       | 7.2
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

I have created a PR (PHP-CS-Fixer/PHP-CS-Fixer#8140) in the PHP-CS-Fixer repo to bring the ``@PER`-CS2.0` ruleset in line with the specifications on the `new_with_parentheses` rule for anonymous classes. Since the ``@Symfony`` ruleset builds upon the ``@PER`-CS2.0` ruleset, they would like confirmation that the Symfony community is OK with this change affecting the Symfony ruleset as well. Should it not be, I'll push another commit there ensuring that the change does not affect ``@Symfony``.

Therefore, this PR is not meant to be merged, but function as an RFC to get your opinion and show the effect it would have when applied to the Symfony source.

Commits
-------

506e0dd327 Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)
symfony-splitter pushed a commit to symfony/routing that referenced this pull request Aug 6, 2024
…`` (parentheses for anonymous classes) (bonroyage)

This PR was squashed before being merged into the 7.2 branch.

Discussion
----------

Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)

| Q             | A
| ------------- | ---
| Branch?       | 7.2
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

I have created a PR (PHP-CS-Fixer/PHP-CS-Fixer#8140) in the PHP-CS-Fixer repo to bring the ``@PER`-CS2.0` ruleset in line with the specifications on the `new_with_parentheses` rule for anonymous classes. Since the ``@Symfony`` ruleset builds upon the ``@PER`-CS2.0` ruleset, they would like confirmation that the Symfony community is OK with this change affecting the Symfony ruleset as well. Should it not be, I'll push another commit there ensuring that the change does not affect ``@Symfony``.

Therefore, this PR is not meant to be merged, but function as an RFC to get your opinion and show the effect it would have when applied to the Symfony source.

Commits
-------

506e0dd327 Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)
symfony-splitter pushed a commit to symfony/framework-bundle that referenced this pull request Aug 6, 2024
…`` (parentheses for anonymous classes) (bonroyage)

This PR was squashed before being merged into the 7.2 branch.

Discussion
----------

Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)

| Q             | A
| ------------- | ---
| Branch?       | 7.2
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

I have created a PR (PHP-CS-Fixer/PHP-CS-Fixer#8140) in the PHP-CS-Fixer repo to bring the ``@PER`-CS2.0` ruleset in line with the specifications on the `new_with_parentheses` rule for anonymous classes. Since the ``@Symfony`` ruleset builds upon the ``@PER`-CS2.0` ruleset, they would like confirmation that the Symfony community is OK with this change affecting the Symfony ruleset as well. Should it not be, I'll push another commit there ensuring that the change does not affect ``@Symfony``.

Therefore, this PR is not meant to be merged, but function as an RFC to get your opinion and show the effect it would have when applied to the Symfony source.

Commits
-------

506e0dd327 Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)
symfony-splitter pushed a commit to symfony/asset-mapper that referenced this pull request Aug 6, 2024
…`` (parentheses for anonymous classes) (bonroyage)

This PR was squashed before being merged into the 7.2 branch.

Discussion
----------

Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)

| Q             | A
| ------------- | ---
| Branch?       | 7.2
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

I have created a PR (PHP-CS-Fixer/PHP-CS-Fixer#8140) in the PHP-CS-Fixer repo to bring the ``@PER`-CS2.0` ruleset in line with the specifications on the `new_with_parentheses` rule for anonymous classes. Since the ``@Symfony`` ruleset builds upon the ``@PER`-CS2.0` ruleset, they would like confirmation that the Symfony community is OK with this change affecting the Symfony ruleset as well. Should it not be, I'll push another commit there ensuring that the change does not affect ``@Symfony``.

Therefore, this PR is not meant to be merged, but function as an RFC to get your opinion and show the effect it would have when applied to the Symfony source.

Commits
-------

506e0dd327 Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)
symfony-splitter pushed a commit to symfony/error-handler that referenced this pull request Aug 6, 2024
…`` (parentheses for anonymous classes) (bonroyage)

This PR was squashed before being merged into the 7.2 branch.

Discussion
----------

Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)

| Q             | A
| ------------- | ---
| Branch?       | 7.2
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

I have created a PR (PHP-CS-Fixer/PHP-CS-Fixer#8140) in the PHP-CS-Fixer repo to bring the ``@PER`-CS2.0` ruleset in line with the specifications on the `new_with_parentheses` rule for anonymous classes. Since the ``@Symfony`` ruleset builds upon the ``@PER`-CS2.0` ruleset, they would like confirmation that the Symfony community is OK with this change affecting the Symfony ruleset as well. Should it not be, I'll push another commit there ensuring that the change does not affect ``@Symfony``.

Therefore, this PR is not meant to be merged, but function as an RFC to get your opinion and show the effect it would have when applied to the Symfony source.

Commits
-------

506e0dd327 Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)
symfony-splitter pushed a commit to symfony/security-http that referenced this pull request Aug 6, 2024
…`` (parentheses for anonymous classes) (bonroyage)

This PR was squashed before being merged into the 7.2 branch.

Discussion
----------

Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)

| Q             | A
| ------------- | ---
| Branch?       | 7.2
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

I have created a PR (PHP-CS-Fixer/PHP-CS-Fixer#8140) in the PHP-CS-Fixer repo to bring the ``@PER`-CS2.0` ruleset in line with the specifications on the `new_with_parentheses` rule for anonymous classes. Since the ``@Symfony`` ruleset builds upon the ``@PER`-CS2.0` ruleset, they would like confirmation that the Symfony community is OK with this change affecting the Symfony ruleset as well. Should it not be, I'll push another commit there ensuring that the change does not affect ``@Symfony``.

Therefore, this PR is not meant to be merged, but function as an RFC to get your opinion and show the effect it would have when applied to the Symfony source.

Commits
-------

506e0dd327 Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)
symfony-splitter pushed a commit to symfony/var-dumper that referenced this pull request Aug 6, 2024
…`` (parentheses for anonymous classes) (bonroyage)

This PR was squashed before being merged into the 7.2 branch.

Discussion
----------

Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)

| Q             | A
| ------------- | ---
| Branch?       | 7.2
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

I have created a PR (PHP-CS-Fixer/PHP-CS-Fixer#8140) in the PHP-CS-Fixer repo to bring the ``@PER`-CS2.0` ruleset in line with the specifications on the `new_with_parentheses` rule for anonymous classes. Since the ``@Symfony`` ruleset builds upon the ``@PER`-CS2.0` ruleset, they would like confirmation that the Symfony community is OK with this change affecting the Symfony ruleset as well. Should it not be, I'll push another commit there ensuring that the change does not affect ``@Symfony``.

Therefore, this PR is not meant to be merged, but function as an RFC to get your opinion and show the effect it would have when applied to the Symfony source.

Commits
-------

506e0dd327 Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)
symfony-splitter pushed a commit to symfony/cache that referenced this pull request Aug 6, 2024
…`` (parentheses for anonymous classes) (bonroyage)

This PR was squashed before being merged into the 7.2 branch.

Discussion
----------

Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)

| Q             | A
| ------------- | ---
| Branch?       | 7.2
| Bug fix?      | no
| New feature?  | no
| Deprecations? | no
| Issues        | -
| License       | MIT

I have created a PR (PHP-CS-Fixer/PHP-CS-Fixer#8140) in the PHP-CS-Fixer repo to bring the ``@PER`-CS2.0` ruleset in line with the specifications on the `new_with_parentheses` rule for anonymous classes. Since the ``@Symfony`` ruleset builds upon the ``@PER`-CS2.0` ruleset, they would like confirmation that the Symfony community is OK with this change affecting the Symfony ruleset as well. Should it not be, I'll push another commit there ensuring that the change does not affect ``@Symfony``.

Therefore, this PR is not meant to be merged, but function as an RFC to get your opinion and show the effect it would have when applied to the Symfony source.

Commits
-------

506e0dd327 Code style change in ``@PER`-CS2.0` affecting ``@Symfony`` (parentheses for anonymous classes)
@keradus
Copy link
Member

keradus commented Aug 7, 2024

thanks @bonroyage

@keradus keradus merged commit 1ce9e24 into PHP-CS-Fixer:master Aug 7, 2024
29 checks passed
@bonroyage bonroyage deleted the new_with_parentheses branch August 7, 2024 17:18
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.

None yet

5 participants