Releases: fs-webdev/eslint-config-tree
6.1.1
- Add cy files to our overrides for tests and non-production code to not include our extra rules that are not needed for that (#21)
For example, we don't need to add test selectors for buttons in our cy
tests.
This will make it so we don't see these warnings (and the like) in our
apps that will have cypress testing:
To-Dos
- Run tests (part of pre-push hook)
- Update demo and tests, if linting configuration is being changed
- Update documentation & README
- Increment package.json version
6.1.0
- Support the new @fs/zion/logical-over-directional (#20)
To get the new @fs/zion/logical-over-directional rule to be applied.
@fs/zion/logical-over-directional is in the jest file for now.
jest stuff is in overrides in the jest file so we can just extend it
from the top level rather than from a overrides.
npm update and update to node 20 and update husky
npm run test:update
6.0.1
6.0.0
- npm update and cut the release like @fs/eslint-config-frontier-react (#18)
Updated because I saw that @fs/eslint-config-frontier-react had cut the
release.
my only concern is the new JSDoc description does not satisfy the regex.
@skye2k2 Could you take a look at that?
Co-authored-by: Clif Bergmann [email protected]
- npm run test:update with latest deps (#17)
Nothing new has been changed in this repo--just updating deps to see
what changes in linting-config.test.js.md
- Add shared linting configuration for QA acceptance tests (#16)
Description
Add shared configuration for our WDIO acceptance tests.
Add fixtures to the test overrides list where certain rules are disabled.
Changes
qa.jsconfiguration added.- Release version
6.0.0-alpha.4. - 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 [email protected]
- 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 [email protected]
- 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 [email protected]
Contributors
Assets 2
6.0.0-alpha.4
- Add shared linting configuration for QA acceptance tests (#16)
Description
Add shared configuration for our WDIO acceptance tests.
Add fixtures to the test overrides list where certain rules are disabled.
Changes
qa.jsconfiguration added.- Release version
6.0.0-alpha.4. - 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 [email protected]
- 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 [email protected]
- 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 [email protected]
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 [email protected]
- 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 [email protected]
- 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 [email protected]
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 [email protected]
- 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 [email protected]
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 [email protected]
- 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 [email protected]
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 [email protected]
- 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 [email protected]