[COMPASS-5062] Should we either fix lint warnings or remove those rules and then treat them as errors? Created: 02/Sep/21 Updated: 10/Jan/24 Resolved: 17/Aug/22 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Tech debt |
| Affects Version/s: | None |
| Fix Version/s: | No version |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Le Roux Bodenstein | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Documentation Changes: | Not Needed |
| Description |
|
What is a lint warning? Something worth mentioning but not fixing? Most (all?) lint warnings I've seen are for missing jsDoc comments. With the recent typescript introduction it seems that the jsDoc comments got removed at the same time as types were added. So if we're moving to typescript them presumably we're never going to add the missing jsDoc comments. So can we disable that rule? I'd like to get to the point where linting only prints errors that we have to fix. |
| Comments |
| Comment by Maurizio Casimirri [ 17/Aug/22 ] |
|
will move this to the tech alignment sync so we can reopen tickets with a specific solution |