fix(eslint-plugin): component-max-inline-declarations animations not being checked properly #313
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.
While working on a fix for #304, I noticed that we could clean up this rule/tests, and so I did. Here's the context of each commit:
First commit: Currently we perform some checks to verify that the received limit is >
-1
. Now, we rely on the schema that can handle it automatically.Second commit: Currently we use the function
getDecoratorPropertyValue
to get the desired property. Now, we use selectors instead.Third commit: The tests are a bit verbose with a lot of annotations and also we don't check if the lines are calculated properly. With this commit, we have cleaner tests with properties checking through
data
.Fourth commit: Fixes #304, before this commit we were calculating animation lines as
string
, however it isn't. Now, it may be checked properly.