1.3.0

Removal of Prettier Support

• We have removed support for Prettier in favor of eslint --fix, which is built-in

Why

Though Prettier is faster, it is actually incompatible with our coding standards. Being over-opinionated it can format code in a way that actually breaks some of our own standards, and can even cause infinite loops if we don't compromise our standards.

I am not keen on changing our coding standards to appease an over-opinionated auto-formatter, especially since eslint --fix will fix the same exact issues, albeit slower.

Maybe we will find a way to support Prettier down the road, but for now there is no way to reconcile the coding standards it breaks, and instead we can rely on eslint --fix (of which many editors have packages for too) instead to achive the same effect.

Other Changes

• This module can now be tested in isolation by itself since it, itself, is configured to extend @webdevstudios/eslint-config-js-coding-standards making testing simpler and more isolated
• Therefore, we've moved over the example/ scripts we use to test linting over from WebDevStudios/coding-standards-dev to this package
• I'm also going to let e.g. npm version minor|major|patch decide and tag the versions, meaning moving forward there with be a v in front of the version, e.g. v1.3.0