-
Notifications
You must be signed in to change notification settings - Fork 619
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
grpc-js is incredibly difficult to lint/prettify/fix #2464
Comments
FWIW - I tried updating GTS to version 4, but the same problems persist |
Here's the full error when trying to run GTS fix:
|
I would support updating or switching the linter. It looks like some actual code changes will also be needed to fix some lint errors. |
dancrumb
added a commit
to dancrumb/grpc-node
that referenced
this issue
Jun 15, 2023
GTS provides config for ESLint, Prettier and TSConfig; this commit removes GTS, but brings over the configuration details Fixes grpc#2464
dancrumb
added a commit
to dancrumb/grpc-node
that referenced
this issue
Jun 15, 2023
sergiitk
pushed a commit
to sergiitk/grpc-node
that referenced
this issue
Jun 28, 2023
Moving from exporting a namespace to just putting assert2 functions into their own files Fixes grpc#2464
sergiitk
pushed a commit
to sergiitk/grpc-node
that referenced
this issue
Jun 28, 2023
GTS provides config for ESLint, Prettier and TSConfig; this commit removes GTS, but brings over the configuration details Fixes grpc#2464
sergiitk
pushed a commit
to sergiitk/grpc-node
that referenced
this issue
Jun 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem description
As a would-be contributor, I'd like to comply with the lining and formatting rules, but it's incredibly difficult to do so.
The current
master
HEAD does not currently pass thelint
script and thefix
script fails.It's also worth noting that this project uses
tslint
which has been deprecated for over 4 years.In short, it's hard to know where to start with the lining and formatting rules since the repo doesn't appear to be in compliance with its own rules.
Reproduction steps
npm install
from the repo rootcd packages/grpc-js/
npm install
npm run lint
First, you get this warning:
npm run fix
Same warning
The command fails with
✖ 15 problems (5 errors, 10 warnings)
Environment
Additional context
This isn't just a nitpick. I'd like to assist with making this package Deno-ready and part of this would include adding lint rules to prevent the direct use of Timer functions so that they can be properly shimmed to support Node and Deno environments.
I'd be happy to put in the work to migrate this repo from
gts
andtslint
toeslint/prettier
.This would make life a lot easier for VSCode users, as well as bring the repo up to date with industry norms (see https://npmtrends.com/eslint-vs-gts-vs-prettier-vs-tslint).
To be clear: I'm not trying to impugn your choice with GTS... it shows/showed a lot of promise, but it seems to have stagnated or, at least, isn't a priority. They created a
4.0.1
version in January, but didn't actually publish it until March and it's still tagged asnext
rather thanlatest
tag.The text was updated successfully, but these errors were encountered: