Open KyleJu opened 4 days ago
@KyleJu can you please assign this to me.
The lint
target is actually looking at JS and TS code, not python.
I believe that the problem is the last part of the command:
lit-analyzer "client-src/elements/chromedash-!(featurelist)*.js"
We no longer have any *.js
files in that directory because they were all converted to *.ts
.
So, the fix is to change the command to also look at *.ts
. However, we have some lit-analyzer errors that need to be addressed as part of that change.
In addition to the problem with npm run lint
commented on above, there is also a problem with npm run pylint
. We need to configure pylint to match our indentation conventions and then address a bunch of remaining lint items.
The linting for Python isn't working currently, as it is not analyzing any files:
e.g https://github.com/GoogleChrome/chromium-dashboard/actions/runs/11823294287/job/32942285509