fix: get correct ruleName without specifying file extension #473
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Userbit
changed the title
SimenB
reviewed
Nov 14, 2019
SimenB
changed the title
github-actions bot
pushed a commit
that referenced
this pull request
Nov 14, 2019
## [23.0.4](v23.0.3...v23.0.4) (2019-11-14) ### Bug Fixes * get correct ruleName without specifying file extension ([#473](#473)) ([f09203e](f09203e))
|
🎉 This PR is included in version 23.0.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In my own VSCode current version of forming url to a rule is incorrect.
Because of after transformation from TypeScript to JavaScript all **.ts file extensions become **.js and hence the below statement is invalid now:
eslint-plugin-jest/src/rules/utils.ts
Line 14 in b4868be
I suggest version that is independent on an extension.