Set maxWarnings as -1 to avoid fail CLI when just warnings

[abdonrd]

First I run the npm run prettier:write command https://github.com/runem/lit-analyzer/commit/89d691f8b669d1b3bf2d9fc339207296cad6b1e9

Fix #94

[runem]

Thank you so much for this PR! I'll go ahead and merge :-)

[abdonrd]

Yay! Thanks @runem! I look forward to a new release! 😀

[abdonrd]

Hi @runem! When we can expect a new version with this? Thanks in advance!

[runem]

I just made this change log by looking at the commit log. These are the changes that will go live with the release of 1.1.11. These changes seem relativ safe to publish. I'll run the final tests and will to make a publish during this week :blush:

• Better performance when using the no-missing-imports rule. lit-analyzer will still check imported modules in your project as usual, however, it will only follow imports 2 levels deep into any imported module from an external dependency (see #93)

• New rule: no-legacy-attribute which is disabled as default. A common mistake when dealing with Lit in particular is to use the legacy Polymer syntax as seen in earlier versions of Polymer (the predecessor of Lit). This rule catches this mistake (see #95)

• The CLI-option maxWarnings defaults to -1 to avoid failing when the analysis found only warnings (see #96)

• Added closure security safe type for <source src> (see #88)

• Fixed typo about event type detection (see #86)

[abdonrd]

Great, thanks @runem!

[runem]

@abdonrd Version 1.1.11 has been published now :-)

[abdonrd]

Thanks @runem! 👏