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

Generic/LowerCaseConstant: move parse error test to its own file #540

Conversation

biinari
Copy link
Contributor

@biinari biinari commented Jul 13, 2024

Description

Suggested changelog entry

N/A

Related issues/external references

See #143

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
    • This change is only breaking for integrators, not for external standards or end-users.
  • Documentation improvement

PR checklist

  • I have checked there is no other PR open for the same change.
  • I have read the Contribution Guidelines.
  • I grant the project the right to include and distribute the code under the BSD-3-Clause license (and I have the right to grant these rights).
  • I have added tests to cover my changes.
  • I have verified that the code complies with the projects coding standards.
  • [Required for new sniffs] I have added XML documentation for the sniff.

Copy link
Member

@jrfnl jrfnl left a comment

Choose a reason for hiding this comment

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

💯 I'll merge this once the build has passed.
Thanks for contributing @biinari!

@jrfnl jrfnl added this to the 3.10.x Next milestone Jul 13, 2024
@jrfnl jrfnl merged commit d0a9809 into PHPCSStandards:master Jul 13, 2024
42 checks passed
@biinari biinari deleted the chore/143-Generic_LowerCaseConstant_separate_parse_error branch July 14, 2024 00:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants