This repository has been archived by the owner on Jul 15, 2023. It is now read-only.
Remove absolute path from rules error messages. #641
Merged
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
PR checklist
New feature,bugfix,or enhancementOverview of change:
export-namenow has only base file name in error message.missing-jsdocremoved filename from error messagereact-no-dangerous-htmlfilename from error messageI haven't changed how string concatenations is made for multiline errors because anyway they will be migrated soon.
Is there anything you'd like reviewers to focus on?
Added inline comment.
This PR with template looks better and important :)