Skip to content
This repository has been archived by the owner on May 15, 2024. It is now read-only.

Fix: update eslint-config-amex to v12 #153

Closed
wants to merge 4 commits into from

Conversation

PixnBits
Copy link
Contributor

Description

Update eslint-config-amex to ^12
Automatic and manual fixes applied.

Motivation and Context

Prevent more issues!

How Has This Been Tested?

locally $ npm run lint -- --fix and $ npm test

Types of Changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation (adding or updating documentation)
  • Dependency update

Checklist:

  • My change requires a change to the documentation and I have updated the documentation accordingly.
  • My changes are in sync with the code style of this project.
  • There aren't any other open Pull Requests for the same issue/update.
  • These changes should be applied to a maintenance branch.
  • This change requires cross browser checks.
  • This change impacts caching for client browsers.
  • This change adds additional environment variable requirements for Holocron users.
  • I have added the Apache 2.0 license header to any new files created.

What is the Impact to Developers Using Holocron?

Gain the assurances of the rules introduced in eslint-config-amex@12

@@ -34,16 +34,19 @@ function parseVersion(raw) {
return raw;
}

const match = /^v?(\d+)\.(\d+)\.(\d+)(?:-(.+))?$/.exec(raw.trim());
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

split out the parsing due to unicorn/no-unsafe-regex calling out the (?:-(.+))? bit

Comment on lines +198 to +199
mapModuleStateToProperties,
mapDispatchToProperties,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this goes against convention..

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good catch!!

@@ -39,7 +39,7 @@
"enzyme": "^3.11.0",
"enzyme-to-json": "^3.2.2",
"eslint": "^6.8.0",
"eslint-config-amex": "^11.2.0",
"eslint-config-amex": "^12.2.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not a fan of props to properties, I believe that this lint rule is removed in later versions.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah! Though that's what "props" is short for I can add an ignore directive before the update to v13 👍

@PixnBits
Copy link
Contributor Author

need to restart due to the prop bit (lots of changes)
maybe it'd be better to move to v13? 🤔

@PixnBits PixnBits closed this Sep 26, 2023
@PixnBits PixnBits deleted the fix/update-eslint-config-amex_12 branch September 26, 2023 22:17
@PixnBits
Copy link
Contributor Author

#157 opened instead

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants