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

[Documentation] PSR12 - Import Statement #232

Merged

Conversation

dingo-d
Copy link
Contributor

@dingo-d dingo-d commented Jan 5, 2024

The PR contains the documentation for the PSR12/Files/ImportStatement sniff.

Description

This PR will add the documentation for the above-mentioned sniff, according to the official standard definitions.

Suggested changelog entry

Add documentation for the PSR12 ImportStatement sniff

Related issues/external references

Part of #148

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.

Hi @dingo-d Thanks for yet another good PR!

When looking this over, my main question is about the code samples: they seem to contain a lot of "fluff", i.e. code which is not directly related to the rule being checked.

Is there a particular reason for that ? Could the code samples be simplified down to a smaller sample which still makes the rule clear ? (and will prevent confusing the import use statement with a trait use statement)

@dingo-d
Copy link
Contributor Author

dingo-d commented Jan 6, 2024

Is there a particular reason for that ? Could the code samples be simplified down to a smaller sample which still makes the rule clear ? (and will prevent confusing the import use statement with a trait use statement)

Tbh no particular reason, I guess I thought having context would help. Even though in that case, actually using or extending some classes would make more sense. Also, having trait use statements there to showcase the difference could be useful.

I will remove the extra 'fluff' and modify the examples 😄 👍🏼

Co-authored-by: Juliette <663378+jrfnl@users.noreply.github.com>
@dingo-d dingo-d force-pushed the documentation/PSR12-files-import-statement branch from ebd74c6 to e39dae0 Compare January 6, 2024 09:28
@jrfnl
Copy link
Member

jrfnl commented Jan 12, 2024

@dingo-d Is this one ready for a final review ?

@dingo-d
Copy link
Contributor Author

dingo-d commented Jan 12, 2024

@dingo-d Is this one ready for a final review ?

Yes 👍🏼

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.

Why are there trait import statements in the code sample ? The sniff does not apply to those. This is confusing.

@dingo-d
Copy link
Contributor Author

dingo-d commented Jan 12, 2024

Why are there trait import statements in the code sample ? The sniff does not apply to those. This is confusing.

Just looked at the tests, where it was added probably to check those won't trigger the sniff.

In the context of the docs it could be confusing. I'll renove them 👍🏼

@dingo-d dingo-d requested a review from jrfnl January 12, 2024 16:55
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.

Thanks @dingo-d ! LGTM.

@jrfnl jrfnl added this to the 3.8.x Next milestone Jan 13, 2024
@jrfnl jrfnl merged commit f0ead32 into PHPCSStandards:master Jan 13, 2024
38 checks passed
jrfnl pushed a commit that referenced this pull request Jan 13, 2024
* Add the documentation for the PSR12 Import Statement sniff
@jrfnl jrfnl modified the milestones: 3.8.x Next, 3.9.0 Jan 19, 2024
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.

2 participants