-
Notifications
You must be signed in to change notification settings - Fork 36
Cleanup II #588
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
Cleanup II #588
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this done by a linting script?
Co-authored-by: rti <rti@users.noreply.github.com>
Yeah - |
Update: Got YAML files working |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't prettier be installed automatically?
❱ ./lint.sh -f
Fixing Linting and Formatting issues in Typescript
[+] Building 66.4s (15/15) FINISHED
=> naming to docker.io/library/wikibase-suite-test-runner-test-runner
Need to install the following packages:
prettier@3.2.5
Ok to proceed? (y)
[error] Cannot find package 'prettier-plugin-organize-imports' imported from /usr/src/test/noop.js
Question: do we lint from the project root now? Or is this another topic? |
I think that's another topic - we're still linting from |
NOTE: DELETE
test/node_modules/
DIRECTORY AND DOCKER IMAGEwikibase-suite-test-runner-test-runner
.So, to be clear, >95% of this - by lines - is formatting and linting cleanup.
Formatting & linting changes:
.ts
,.mjs
,.json
files - had to add to a few overrides to format JSONs correctlyeslint
packages and pluginsprettier
andprettier-plugin-organize-imports
- make formatting consistent, organize importsyaml-eslint-parser
- formatting and linting YAML files withprettier
andeslint
Actual code changes:
async () => {}
is nowasync function () {}
. Ran into an issue that this fixed a few weeks ago - the context is different between the two, so things likethis.retries()
doesn't actually do anything.retries
to the flakyspecial-property.ts
test.lint.sh
script was wrong - it was trying to lint twice, because it previously linted both/test
and/docs
engine
to14.14
-eslint
caught that we were using features too advanced for10
, specificallyfsPromises
lint:fix:lint
, which just runseslint
, andlint:fix:format
, which just runsprettier
, and changedlint:fix
to run both