Skip to content
This repository has been archived by the owner on Mar 25, 2021. It is now read-only.

Allow Conflicting Rules to Exist but not Be Concurrently Enabled #739

Closed
jkillian opened this issue Oct 16, 2015 · 1 comment
Closed

Allow Conflicting Rules to Exist but not Be Concurrently Enabled #739

jkillian opened this issue Oct 16, 2015 · 1 comment
Labels
Difficulty: Hard Status: Accepting PRs Type: Enhancement
Milestone
TSLint 5.x

Comments

@jkillian
Copy link
Contributor

Recently, we had an issue where we added a new rule that conflicted with a previous rule (see #711). We also have a rule PR that could conflict with future rules (see #722).

To solve these kinds of issues, I propose that TSLint at startup checks its configuration for conflicts, and prints an error and/or aborts if a conflict is found.
@jkillian jkillian added this to the TSLint 4.0 milestone Oct 16, 2015
@jkillian jkillian mentioned this issue May 20, 2016
Closed
@adidahiya adidahiya modified the milestones: TSLint v4.x, TSLint 5.x Mar 30, 2017
@JoshuaKGoldberg
Copy link
Contributor

This seems like it won't be happening.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Difficulty: Hard Status: Accepting PRs Type: Enhancement
Projects
None yet
Milestone
TSLint 5.x
Development

No branches or pull requests
3 participants
@adidahiya @jkillian @JoshuaKGoldberg