6.0.0-alpha.3

• Remove preinstall to see if that is causing issues with prerender-service (#15)

update @fs/eslint-config-frontier-react too, see
fs-webdev/eslint-config-frontier-react#38

This is the issue in prerender-service, so seeing if this will fix this.

• Re-enable tests

NOTE: This build will fail. From now on, we should be reviewing new changes regularly and making informed decisions about the changes to various rules.

• Add Travis CI-based publishing (#14)

Add .travis.yml configuration and @fs/npm-publisher dependency and build step.
Disable tests, to get an already-released version out to artifactory.

TODO: Review the rule changes, and cut a new release.

---

Co-authored-by: Clif Bergmann cbergmann@familysearch.org

• Update cognitive-complexity number (#13)

Change cognitive-complexity back to 25 for most files
Make test files and such have complexity of 50

• Update to latest eslint-config-frontier-react (#12)

See fs-webdev/eslint-config-frontier-react#37

• v6-alpha (#11)

Major release: v6-alpha

Consume latest eslint-config-frontier-react.
Remove all Polymer-based, Code Climate-related, and legacy configuration and documentation.
Upgrade eslint to version 8.
Update snapshots to take all new rules into account.
Centralize all of our typical overrides (.ts, .stories, .test, etc.), and compartmentalize into its own es6.js file.

---

Co-authored-by: Clif Bergmann cbergmann@familysearch.org

• Compare Final Config for Testing (#10)

Print out final eslint config with the rules sorted alphabetically.
Compare the config to the previous reason in a new test.
Clean up output files to strip out environment-specific data via node script, as sed was causing too many issues.
Update documentation.

---

Co-authored-by: Clif Bergmann cbergmann@familysearch.org

6.0.0-alpha.2

• Update cognitive-complexity number (#13)

Change cognitive-complexity back to 25 for most files
Make test files and such have complexity of 50

• Update to latest eslint-config-frontier-react (#12)

See fs-webdev/eslint-config-frontier-react#37

• v6-alpha (#11)

Major release: v6-alpha

Consume latest eslint-config-frontier-react.
Remove all Polymer-based, Code Climate-related, and legacy configuration and documentation.
Upgrade eslint to version 8.
Update snapshots to take all new rules into account.
Centralize all of our typical overrides (.ts, .stories, .test, etc.), and compartmentalize into its own es6.js file.

---

Co-authored-by: Clif Bergmann cbergmann@familysearch.org

• Compare Final Config for Testing (#10)

Print out final eslint config with the rules sorted alphabetically.
Compare the config to the previous reason in a new test.
Clean up output files to strip out environment-specific data via node script, as sed was causing too many issues.
Update documentation.

---

Co-authored-by: Clif Bergmann cbergmann@familysearch.org

6.0.0-alpha.1

• Update to latest eslint-config-frontier-react (#12)

See fs-webdev/eslint-config-frontier-react#37

• v6-alpha (#11)

Major release: v6-alpha

Consume latest eslint-config-frontier-react.
Remove all Polymer-based, Code Climate-related, and legacy configuration and documentation.
Upgrade eslint to version 8.
Update snapshots to take all new rules into account.
Centralize all of our typical overrides (.ts, .stories, .test, etc.), and compartmentalize into its own es6.js file.

---

Co-authored-by: Clif Bergmann cbergmann@familysearch.org

• Compare Final Config for Testing (#10)

Print out final eslint config with the rules sorted alphabetically.
Compare the config to the previous reason in a new test.
Clean up output files to strip out environment-specific data via node script, as sed was causing too many issues.
Update documentation.

---

Co-authored-by: Clif Bergmann cbergmann@familysearch.org

6.0.0-alpha.0

• v6-alpha (#11)

Major release: v6-alpha

Consume latest eslint-config-frontier-react.
Remove all Polymer-based, Code Climate-related, and legacy configuration and documentation.
Upgrade eslint to version 8.
Update snapshots to take all new rules into account.
Centralize all of our typical overrides (.ts, .stories, .test, etc.), and compartmentalize into its own es6.js file.

---

Co-authored-by: Clif Bergmann cbergmann@familysearch.org

• Compare Final Config for Testing (#10)

Print out final eslint config with the rules sorted alphabetically.
Compare the config to the previous reason in a new test.
Clean up output files to strip out environment-specific data via node script, as sed was causing too many issues.
Update documentation.

---

Co-authored-by: Clif Bergmann cbergmann@familysearch.org

5.0.3

• Initial cleanup (#9)

Update linting results to include latest error format for eslint-config-bestpractices.
Move eslint warning from index.js to test file.
Remove extra directory from linting results.

5.0.2

• allow 'finally' to be chained onto a promise (#8)

• allow 'finally' to be chained onto a promise

• version bump

5.0.1

• Increase the cognitive complexity threshold

React function-based code is naturally +3 to +8 complexity, and is triggering all over the place, without developers having a viable solution.
Add overrides note to help developers not make terrible decisions.

• Update README to include another solution for common problems
• Update docs to include help for jsdoc warnings

5.0.0

• Update linting dependencies & documentation (#7)

Update all linting subdependencies.
Add new rules, trigger, and enforce via tests.
Set defaults for some rules.
Add best practices and examples for managing linting in varying projects.

Release version 5.0.0.

4.0.1

• Pin back eslint-plugin-import since it's breaking us. (#6)

4.0.0

• Remove redundant rules
• eslint-plugin-no-only-tests
• eslint-plugin-no-skip-tests
  These rules are now implemented by jest/no-disabled-tests & jest/no-focused-tests.
  Update test snapshot.

Release version 4.0.0.