#44216 closed enhancement (invalid)
Some core files are not fully compatible to WordPress-Core standards
Reported by: | subrataemfluence | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | General | Keywords: | dev-feedback |
Focuses: | coding-standards | Cc: |
Description
I am not sure if this is the right place to ask this question but I have noticed some files have sniffing issues. I have used PHPCS WordPress-Core standard to review and immediately found some.
Are these issues left behind on purpose?
Change History (5)
#1
@
7 years ago
- Focuses coding-standards added
- Milestone Awaiting Review deleted
- Resolution set to invalid
- Status changed from new to closed
- Version trunk deleted
#2
@
7 years ago
Thank you for your quick reply.
May I do some patching focusing coding-standard
keyword?
#3
@
7 years ago
I think the best place to check is the #coding-standards channel in WordPress Slack.
Note: See
TracTickets for help on using
tickets.
Yeah this is a known issue. There's a large number of coding standards violations in core.
Have a read through #41057 for all the background and the big change that fixed a huge number of the issues in [42343].
The
coding-standards
keyword is being used on Trac to track individual issues: https://core.trac.wordpress.org/query?status=!closed&focuses=~coding-standardsI'll close this ticket in favour of the more specific tickets that have that keyword.