• eslint rule: no-param-reassign
• severity:warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: import/no-default-export
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: @typescript-eslint/naming-convention
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: @typescript-eslint/no-unsafe-member-access
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: no-promise-executor-return
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

It is currently not possible to re-export a mock object which should be able to be done like so:

import { MockAxios } from "@rsm-hcd/javascript-testing";
export default MockAxios.default;

MockAxios is getting imported as undefined

• eslint rule: @typescript-eslint/unbound-method
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

Provide instructions around forking, issues, PRs, etc.

• eslint rule: import/no-named-as-default
• severity:warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: @typescript-eslint/no-throw-literal
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: @typescript-eslint/no-unnecessary-type-constraint
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

Migrate from https://github.com/rsm-hcd/AndcultureCode.JavaScript.React to https://github.com/rsm-hcd/hcd-javascript

Instructions to pull git history over: https://stackoverflow.com/a/14992078/203857

git subtree add --prefix=packages/javascript-react https://github.com/rsm-hcd/AndcultureCode.JavaScript.React.git main

• eslint rule: no-extend-native
• severity:warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: @typescript-eslint/no-confusing-void-expression
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: @typescript-eslint/no-unsafe-return
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: @typescript-eslint/no-explicit-any
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

Migrate from https://github.com/rsm-hcd/AndcultureCode.JavaScript.Core to https://github.com/rsm-hcd/hcd-javascript

Instructions to pull git history over: https://stackoverflow.com/a/14992078/203857

git subtree add --prefix=packages/javascript-core https://github.com/rsm-hcd/AndcultureCode.JavaScript.Core.git main

• eslint rule:no-console
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: @typescript-eslint/no-shadow
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: @typescript-eslint/no-unsafe-call
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: @typescript-eslint/no-unnecessary-condition
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

pnpm should be able to publish public packages without the need for a node script to massage the package.json file

• eslint rule: @typescript-eslint/no-misused-promises
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: import/no-named-as-default-member
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule:no-await-in-loop
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

Migrate from https://github.com/rsm-hcd/AndcultureCode.JavaScript.React.Components to https://github.com/rsm-hcd/hcd-javascript

Instructions to pull git history over: https://stackoverflow.com/a/14992078/203857

git subtree add --prefix=packages/javascript-react-components https://github.com/rsm-hcd/AndcultureCode.JavaScript.React.Components.git main

• eslint rule: @typescript-eslint/no-unsafe-assignment
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: @typescript-eslint/no-unsafe-argument
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: @typescript-eslint/no-empty-function
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: @typescript-eslint/require-await
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: no-constant-binary-expression
• severity:warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: @typescript-eslint/no-floating-promises
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: new-cap
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: @typescript-eslint/require-await
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: @typescript-eslint/no-non-null-assertion
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: func-names
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• Add manual publishing instructions to the README
• Setup a way automatically publish to npm
• change docs deployment to only happen at time of publish

Migrate https://github.com/rsm-hcd/AndcultureCode.JavaScript.Testing to https://github.com/rsm-hcd/hcd-javascript

Instructions to pull git history over: https://stackoverflow.com/a/14992078/203857

• eslint rule: @typescript-eslint/explicit-function-return-type
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: no-prototype-builtins
• severity:warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: @typescript-eslint/no-redundant-type-constituents
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: @typescript-eslint/ban-types
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: @typescript-eslint/require-array-sort-compare
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.

• eslint rule: @typescript-eslint/ban-ts-comment
• severity: warn or error

Instructions:

If rule override exists, start with deleting the rule(s) associated with it, and then make code changes to get the linter to be happy.