-
-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: require-exact-type detects nested objects #441
feat: require-exact-type detects nested objects #441
Conversation
…s, including nested ones. Also added a fixer.
@@ -19,7 +19,7 @@ | |||
"chai": "^4.2.0", | |||
"eclint": "^2.8.1", | |||
"eslint": "^5.13.0", | |||
"eslint-config-canonical": "^17.3.4", | |||
"eslint-config-canonical": "^18.1.1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This dependency was causing an error because in this commit import-js/eslint-plugin-import@1a3a128 one of the dependent rules was updated.
@@ -88,7 +88,7 @@ const generateOrderedList = (context, sort, properties) => { | |||
const beforePunctuator = source.getTokenBefore(nextPunctuator, { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reported by rules when I updated the plugin (prefer slice to substring)
@@ -7,199 +7,199 @@ export default { | |||
// "always" (by default) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Keys were unordered (linting rule)
🎉 This PR is included in version 4.7.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
require-exact-type should now detect all object type declarations, not just type aliases. It will also check for nested notations (#376 ).
Also added a fixer.