1.0.0 • Published 4 years ago

@webdevstudios/coding-standards-dev v1.0.0

Weekly downloads
-
License
GPL-3.0-or-later
Repository
github
Last release
4 years ago

WebDevStudios Branding

Coding Standards DEV Environment

Ping @aubreypwd on Twitter if you need help or have any questions.


This is an environment to develop WDS Coding Standards, which include:

Just clone this repoitory somewhere and run:

npm install

This will clone the @webdevstudios/css|js|eslint-coding-standards module repos down and install them locally, meaning node_modules/@webdevstudios/*-coding-standards will symlink automatically to the cloned down repos:

Screenshot of how this symlinking works.

This allows you to dev npm modules via Git as well as have them installed for testing.

If you use nvm you can use nvm use to switch the the preferred node version.

Then run:

composer install

This will install webdevstudips/php-coding-standards:dev-master which will clone the repo to vendor/webdevstudios/php-coding-standards and install it too, again allowing you to dev it in Git and have it installed.

examples/

The content in examples/ are used to test that proper error reporting is (or is not) happening.

npm run watch

When you run npm run watch it will watch for any changes, and will re-install all the modules (e.g. if you chage dependancies, etc).


Changelog

Note, this project is NOT using any tagging anymore, the tags listed are old tags I didn't want to delete.

Friday, 9/18/2020

  • A slimer version of the suite was created that uses less scripts to do the same things.

1.0.0

  • Global stuff officially deprecated

1.0.0-alpha2

  • Test for @wordpress/dependency-group rule
  • Added SASS tests when running npm run tests
  • Fixed issue where phpcs does not get installed in vendor/bin

1.0.0-alpha1

  • Installed .sass-lint.yml file to extend css coding standards lint file
  • Added test-styles command to run SASS tests
  • Moved all scripts to scripts/
  • Automated initial npm install

0.3

  • Fixed issue where js.js wouldn't test out because of missing @wordpress/eslint-plugin
  • Added install, uninstall that just run dev- varients
  • Added reset command to reset everything
  • Added tests command to test all *.js and *.php files in tests/ folder

0.2

  • Setup to be just a repo for working on CS, not a wp-content/ project style
  • Added npm run install-dev to setup this environment to work on coding standards

0.1

  • Working version as a good ol' wp-content/ structure