Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(eslint-plugin): component-max-inline-declarations animations not being checked properly #313

Conversation

rafaelss95
Copy link
Member

@rafaelss95 rafaelss95 commented Jan 23, 2021

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.

@rafaelss95 rafaelss95 force-pushed the fix/component-max-inline-declarations branch 2 times, most recently from 5eff241 to 417ced6 Compare January 24, 2021 05:57
@rafaelss95 rafaelss95 changed the title fix(eslint-plugin): component-max-inline-declarations animations expressions not being checked properly fix(eslint-plugin): component-max-inline-declarations animations not being checked properly Jan 24, 2021
@rafaelss95 rafaelss95 force-pushed the fix/component-max-inline-declarations branch 3 times, most recently from 222358f to 7d57a41 Compare January 25, 2021 16:24
Copy link
Member

@JamesHenry JamesHenry left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fixes! Got some notes inline

@JamesHenry JamesHenry added the BREAKING CHANGE This is a breaking change and should only be released as part of a new major version label Feb 2, 2021
@JamesHenry JamesHenry added this to the v2 milestone Feb 2, 2021
@rafaelss95 rafaelss95 force-pushed the fix/component-max-inline-declarations branch from 7d57a41 to 3f0ab15 Compare February 2, 2021 12:47
@rafaelss95 rafaelss95 force-pushed the fix/component-max-inline-declarations branch from 3f0ab15 to 12bf62b Compare February 2, 2021 12:47
@rafaelss95 rafaelss95 force-pushed the fix/component-max-inline-declarations branch from 12bf62b to 5cd7e35 Compare February 2, 2021 13:13
@JamesHenry JamesHenry merged commit 61a2a0f into angular-eslint:master Feb 6, 2021
@JamesHenry JamesHenry removed the BREAKING CHANGE This is a breaking change and should only be released as part of a new major version label Feb 6, 2021
@JamesHenry JamesHenry removed this from the v2 milestone Feb 6, 2021
@rafaelss95 rafaelss95 deleted the fix/component-max-inline-declarations branch February 6, 2021 19:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

@angular-eslint/component-max-inline-declarations" rule not works properly with animations
2 participants