chore(project): remove alex linter

docs/developer-handbook.md

@@ -260,14 +260,10 @@ The subject contains a succinct description of the change:
 
 ### Body
 
-<!-- alex disable just -->
-
 Just as in the subject, use the imperative, present tense: "change" not
 "changed" nor "changes". The body should include the motivation for the change
 and contrast this with previous behavior.
 
-<!-- alex enable just -->
-
 ### Footer
 
 The footer should contain any information about Breaking Changes.

docs/guides/accessibility.md

@@ -1,5 +1,3 @@
-<!-- alex disable failure -->
-
 # Accessibility
 
 <!-- prettier-ignore-start -->
@@ -152,15 +150,11 @@ component with the necessary keyboard functionality.
 
 ### Screen magnifier testing🔎
 
-<!-- alex disable his -->
-
 (Credit to Frederick Creemers
 [excellent article](https://dev.to/_bigblind/how-to-make-your-website-accessible-to-people-who-use-a-screen-magnifier)
 talking about his experience as a visually impaired screen magnification user on
 the web.)
 
-<!-- alex enable his -->
-
 A user with a screen magnifier views web content on a component by component
 basis through a 2x, 4x, or 8x (etc) zoomed in box. Two things become very
 important when using a screen magnifier -- context and component permanence. We

docs/guides/colors.md

@@ -1,5 +1,3 @@
-<!-- alex disable colors -->
-
 # Colors
 
 <!-- prettier-ignore-start -->

docs/guides/endgame.md

@@ -1,5 +1,3 @@
-<!-- alex disable black -->
-
 # Endgame
 
 <!-- prettier-ignore-start -->

docs/guides/sass.md

@@ -1,5 +1,3 @@
-<!-- alex disable color -->
-
 # Sass
 
 <!-- prettier-ignore-start -->

docs/guides/setup/design.md

@@ -1,5 +1,3 @@
-<!-- alex disable color -->
-
 # Design
 
 <!-- prettier-ignore-start -->

docs/guides/support.md

@@ -1,5 +1,3 @@
-<!-- alex disable failures -->
-
 # Carbon core support and maintenance
 
 <!-- prettier-ignore-start -->

docs/guides/triaging-accessibility-issues.md

@@ -1,5 +1,3 @@
-<!-- alex disable failure -->
-
 # Triaging a new Accessibility Issue
 
 ## Severity

docs/migration/10.x-color.md

@@ -1,5 +1,3 @@
-<!-- alex disable color -->
-
 # Colors
 
 <!-- prettier-ignore-start -->

docs/migration/10.x-themes.md

@@ -1,5 +1,3 @@
-<!-- alex disable color -->
-
 # Themes
 
 <!-- prettier-ignore-start -->

docs/on-windows-hcm-support.md

@@ -1,5 +1,3 @@
-<!-- alex disable colors -->
-
 <!-- START doctoc generated TOC please keep comment here to allow auto update -->
 <!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
 

docs/postmortems/2019-08-15-icons-angular.md

@@ -60,8 +60,6 @@ This issue was first reported by @cal-smith
 
 **Where we got lucky**
 
-<!-- alex disable period -->
-
 - We were still within the 72 hour time period required by `npm` for their
   `unpublish` feature to work
 

docs/postmortems/2019-10-07-content-switcher-breaking-change.md

@@ -29,8 +29,6 @@ the Carbon Design System, notably `10.6.x` and `7.6.x` ranges.
 <!-- Looking back, what ended up being the main reasons why this event occurred?
 -->
 
-<!-- alex disable hooks -->
-
 We targeted `ContentSwitcher` as a good candidate for a React hooks migration.
 Unfortunately, the migration updated parts of the public API in a
 semver-incompatible way causing a breaking change.

docs/postmortems/2020-04-09-v10.11.0-release.md

@@ -3,8 +3,6 @@ date: 2020-04-09
 authors: joshblack
 ---
 
-<!-- alex disable colors -->
-
 # v10.11.0 Release
 
 **Summary**

docs/postmortems/README.md

@@ -1,5 +1,3 @@
-<!-- alex disable failure -->
-
 # Postmortems
 
 > A postmortem is a written record of an incident, its impact, the actions taken

docs/style.md

@@ -1,5 +1,3 @@
-<!-- alex disable hooks -->
-
 <!--
 Inspired by Uber's Go Style Guide:
 https://github.com/uber-go/guide/blob/85bf203f4371a8ae9e5e9a4d52ea77b17ca04ae6/style.md

package.json

@@ -24,7 +24,6 @@
     "format": "prettier --write '**/*.{js,md,scss,ts}' '!**/{build,es,lib,storybook,ts,umd}/**'",
     "format:diff": "prettier --list-different '**/*.{js,md,scss,ts}' '!**/{build,es,lib,storybook,ts,umd}/**' '!packages/components/**'",
     "lint": "eslint actions config codemods packages",
-    "lint:docs": "alex 'docs/**/*.md' -q",
     "lint:styles": "stylelint '**/*.{css,scss}' --report-needless-disables --report-invalid-scope-disables",
     "sync": "carbon-cli sync",
     "test": "cross-env BABEL_ENV=test jest",
@@ -48,7 +47,6 @@
     "@commitlint/cli": "^8.3.5",
     "@commitlint/config-conventional": "^8.3.4",
     "@ibma/aat": "https://able.ibm.com/tools/dist/ibma-aat-2.0.6.tgz",
-    "alex": "^8.0.0",
     "axe-core": "^3.3.2",
     "babel-jest": "^26.0.1",
     "cross-env": "^5.2.0",
@@ -129,7 +127,6 @@
       "git add"
     ],
     "!(*sass).md": [
-      "alex",
       "prettier --write",
       "git add"
     ]

packages/cli/src/commands/ci-check.js

@@ -23,7 +23,6 @@ async function check(args, env) {
   const tasks = [
     'yarn format:diff',
     'yarn lint --quiet',
-    'yarn lint:docs',
     'yarn lint:styles',
     `yarn bundler check --ignore '**/@(node_modules|examples|components|react|fixtures)/**' 'packages/**/*.scss'`,
     `cross-env BABEL_ENV=test yarn test --ci --maxWorkers 2 --reporters=default --reporters=jest-junit`,

packages/icons/README.md

@@ -89,8 +89,6 @@ svg [data-icon-path='inner-path'] {
 }
 ```
 
-<!-- alex ignore color -->
-
 In the code snippet above, we are targetting the inner path attribute with
 `[data-icon-path="inner-path"]`. The value of `fill` will be the custom color
 you would like to set for the inner path. We also need to set `opacity` to `1`