-
Notifications
You must be signed in to change notification settings - Fork 292
feat: adopt linter #333
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
feat: adopt linter #333
Conversation
Signed-off-by: Sebastian Beltran <[email protected]>
Signed-off-by: Sebastian Beltran <[email protected]>
Signed-off-by: Sebastian Beltran <[email protected]>
Signed-off-by: Sebastian Beltran <[email protected]>
Signed-off-by: Sebastian Beltran <[email protected]>
Signed-off-by: Sebastian Beltran <[email protected]>
Signed-off-by: Sebastian Beltran <[email protected]>
Signed-off-by: Sebastian Beltran <[email protected]>
Signed-off-by: Sebastian Beltran <[email protected]>
Pull Request Test Coverage Report for Build 17015694733Details
💛 - Coveralls |
Signed-off-by: Sebastian Beltran <[email protected]>
|
I've reviewed the changes several times, it only removes spaces, so it reduces lines of code, and that's why the build gets smaller. |
|
I added a .git-blame-ignore-revs so the blame doesn’t get messed up with these changes |
|
FYI: We are working on merging |
|
Ohhh, wow, I’m glad to hear that, that would be super cool |


Neostandard is being adopted as the linter. In Express we currently use Standard, but we’re planning to change it, though we don’t yet know which one. Anyway, there’s no issue in adopting this linter :), and it will also help us run type tests for this package, which I’ll try to add in a following PR after this one is merged