Coding standards check - don't use WordPress about wprig HOT 4 CLOSED

@dingo-d Can you create a PR for this?

from wprig.

Sure thing, on it :)

EDIT:

Ok so I wanted to test it, but for some reason, it's not picking the WordPress-Themestandard in the phpcs.xml.dist file.

If anyone wants to test it, modify the composer with this:

{
    "name": "wprig/wprig",
    "description": "A progressive theme development rig for WordPress.",
    "type": "wordpress-theme",
    "license": "GPL-2.0",
    "require-dev": {
        "wp-coding-standards/wpcs": "dev-feature/theme-review-sniffs",
        "dealerdirect/phpcodesniffer-composer-installer": "^0.4.4",
        "wimg/php-compatibility": "^8.1"
    },
    "repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/WPTRT/WordPress-Coding-Standards"
        }
    ]
}

and in the phpcs.xml.dist modify the rules

<rule ref="WordPress"/>
<rule ref="WordPress-Core" />
<rule ref="WordPress-Docs" /> 
<rule ref="WordPress-Extra" />

and replace it with

<rule ref="WordPress-Theme" />

I'll see what could be the issue. In the meantime, I can submit the PR with updated composer.json and removed WordPress and WordPress-Core standards from the ruleset (so that VIP and Core are not included).

Once the new repository for the WordPress-Theme coding standards is created I will submit a new PR.

Thoughts?

from wprig.

WPCS was updated to 1.0.0 which means this is no longer relevant. Closing.

from wprig.

I'll create a PR once we defork the Theme coding standards

from wprig.