-
Notifications
You must be signed in to change notification settings - Fork 9
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 errors #16
Comments
Hey @NicolasRitouet i would like to try on this. |
@Logan1x Great! |
@Logan1x |
I'm going to tackle this. |
Hey John,
Khushal already offered to work on this, can you coordinate with him to see
how you could split the work?
Le sam. 29 juil. 2017 à 13:45, John Scetinin <[email protected]> a
écrit :
… I'm going to tackle this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#16 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAMhTuvDtBKYotzF0RrKl5Ik0dandWRAks5sSxtUgaJpZM4OdsTI>
.
|
@Logan1x, Hi Kushal, could you provide status on your contribution? I wonder if we could split it up and fix those issues together? |
I am @NicolasRitouet i am busy these days can you pass on someone else.Thanks. |
Hey @NicolasRitouet ! Is this issue still up for grabs? I would like to work on it. |
When we introduced eslint to the
deployd-cli
codebase, a few eslint rules were throwing errors.In order to move fast, I decided to change the rules and throw warning instead of errors for a few rules.
In order to have a clean codebase, we need to fix the code to allow eslint to throw normal errors for these rules.
ℹ️ This ticket has been labeled
first-timers-only
, it means that it's only available for people who never contributed to an open-source project. Feel free to ask questions and get help on gitter.Todo
You can also send one PR per reactivated rules if you prefer.
rules to reactivate
The text was updated successfully, but these errors were encountered: