This repository has been archived by the owner on Jul 15, 2023. It is now read-only.
Proposal: Remove absolute paths from error messages (ideally before 6.0) #634
Labels
Difficulty: Easy
Someone with little to no experience in TSLint should be able to send a pull request for this issue.
Domain: Tooling
Repository tasks around improving source tooling.
Status: Accepting PRs
Type: Rule Feature
Adding a feature to an existing rule.
Milestone
Absolute paths block micration to TSLint test format, since error message will depend on file location, and can't be universal across Windows/Linux/Mac OS.
File name/path should be in formatter output (I've checked all core formatters and they provide absolute path).
There are 3 rules that use absolute path in its erros:
export-name
source - use file base name - will be easy to compare.missing-jsdoc
source (already deprecated in this repo) - remove absolute path and change:
to.
at the end of error message.react-no-dangerous-html
- source - remove absolute path andof source file
string before it.What do you think? How critical to have absolute path here (especially last one)?
As for me - it will make error messages hard to read, because path can be too long.
In IDE I'm already in that file and in CI formatter will output path relative to
The text was updated successfully, but these errors were encountered: