Summary:
And run `npm run p:w .` for that, and add .prettierignore so `sh` plugin ignores them.
Signed-off-by: Yongmin Hong <revi@omglol.email>
Test Plan: `npm run p:c .` and `npm publish`.
Reviewers: O1 revi & automations, revi
Reviewed By: O1 revi & automations, revi
Differential Revision: https://issuetracker.revi.xyz/D355
Summary:
Signed-off-by: Yongmin Hong <revi@omglol.email>
npm: use @revi/eslint-config
Also change eslint format, and publish `v0.0.2`.
Also prepare for eslint-config-wikimedia when they have eslint9 support.
Signed-off-by: Yongmin Hong <revi@omglol.email>
Test Plan: `npm run eslint`.
Reviewers: O1 revi & automations, revi
Reviewed By: O1 revi & automations, revi
Differential Revision: https://issuetracker.revi.xyz/D332
Summary:
Shared config testbed, yeah.
Signed-off-by: Yongmin Hong <revi@omglol.email>
Test Plan: `npm run p:c .` should run as it is.
Reviewers: O1 revi & automations, revi
Reviewed By: O1 revi & automations, revi
Differential Revision: https://issuetracker.revi.xyz/D305
Summary:
Docs: https://prettier.io/docs/en/configuration#sharing-configurations
To be published @ npm and imported elsewhere.
Signed-off-by: Yongmin Hong <revi@omglol.email>
Test Plan: no test can be performed at this time; needs to be landed, published to npm, and then we can test from other tepo importing this.
Reviewers: O1 revi & automations, revi
Reviewed By: O1 revi & automations, revi
Differential Revision: https://issuetracker.revi.xyz/D302
