Extract rule: template-no-ambiguous-glimmer-paths#2401
Closed
NullVoxPopuli wants to merge 1 commit intoember-cli:masterfrom
Closed
Conversation
NullVoxPopuli
force-pushed
the
nvp/template-lint-extract-rule-template-no-ambiguous-glimmer-paths
branch
from
ce5a4eb to
c9479f2
Compare
NullVoxPopuli
force-pushed
the
nvp/template-lint-extract-rule-template-no-ambiguous-glimmer-paths
branch
from
c9479f2 to
1184a13
Compare
Contributor
Author
|
We don't need this one either, because we catch problems earlier at compile time (and no-unused covers us as well) |
NullVoxPopuli
deleted the
nvp/template-lint-extract-rule-template-no-ambiguous-glimmer-paths
branch
This file contains hidden or 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Split from #2371.