JavaScriptEnhancements Unused variables

I just tested it a bit on a new updated version (0.13.14) and there's a couple more issues with unused variables.

And another caused by mixing return + template literal.

Jan 24 '18 09:01 ilearnio

@ilearnio ok! The problem is that there could be so many cases! Thanks for your support!! 👍

Jan 24 '18 12:01 pichillilorenzo

Updated! 👍

Jan 25 '18 01:01 pichillilorenzo

Fantastic! Thanks!

Jan 25 '18 10:01 ilearnio

Hi, thanks for the awesome package. And there is still an issue. Case: screenshot from 2018-01-28 23-08-50 when used function arguments destructuring.

Jan 28 '18 17:01 talgat-ruby

@talgat-ruby Ok, I will check about that!

Jan 28 '18 17:01 pichillilorenzo

@talgat-ruby Try the new version 0.15.0 and let me know!

Feb 11 '18 18:02 pichillilorenzo

Hi @pichillilorenzo . Thanks yeah the problem resolved. But it was just removed. For example screenshot from 2018-02-13 12-48-18

The props probably must light, because we do not use it. Thanks.

P.S. I am not good with python, otherwise I would love to help you with improvements of the package

Feb 13 '18 06:02 talgat-ruby

Mmmm yeah I didn't consider class properties! I will check also about that thanks 👍

Feb 13 '18 07:02 pichillilorenzo

One more case code boxes meetyourstar-admin src renderer store

Feb 13 '18 07:02 ilearnio

Feb 13 '18 09:02 ilearnio

Found another one. Happens only when there is an exclamation mark in if statement.

Feb 19 '18 14:02 ilearnio

@ilearnio ok, sorry if it is taking time to release the new update but i'm refactoring all the code in certain way that it won't require anymore my "workaround" described in the CONTRIBUTING.md file, in order to let people understand better all of my code!

Feb 19 '18 14:02 pichillilorenzo

@pichillilorenzo it's ok. I just posting you issues I find

Feb 19 '18 14:02 ilearnio

I have updated it!

Mar 11 '18 22:03 pichillilorenzo

It doesn't check used variables in flow's type annotations. (v0.16.1)