Repository navigation
build(deps): bump @exadev/eslint-config to 3.0.0 - #68
Conversation
Package manifests, tsconfig files, the Turborepo pipeline and the wrangler config list their keys in alphanumeric order, so a key's position is predictable and a new one has an obvious place.
Source tests carry a `unit` suffix before `.test`, the suites under `test/integration` an `integration` suffix, and the built-package smoke and declaration checks and the workerd suite an `e2e` suffix. The vitest project globs and turbo inputs that name individual files follow the renames.
…rules require Blank lines separate statements, trailing line comments sit above the code they describe, multi-line comments take the doc-comment form, class members are separated, and exported helpers declare their return types.
`exadevConfig` takes its options alone in 3.0.0, so each config spreads its result inside `defineConfig` and lists its own blocks after it. The `consistent-type-imports` overrides declare the TypeScript globs they apply to, since the shared config's plugins are scoped to file globs. Declarations that must keep their released shape (the published `count` signature, the evaluator's positional parameters, the async driver's sequential awaits and the fixtures' sequential seeding) are exempted from the rule that now flags them by a files-scoped override stating why.
5be512e to
d27d58e
Compare
|
@codex security review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
🛡️ Codex Security ReviewSecurity review completed. No security issues were found in this pull request. Reviewed commit: Only the user who started this review can view the report in Codex. ℹ️ About Codex security reviews in GitHubThis is an experimental Codex feature. Security reviews are triggered when:
Once complete, Codex will leave suggestions, or a comment if no findings are found. |
|
🎉 This PR is included in trilean-regex@1.0.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in trilean@1.7.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in trilean-sql@2.2.5 🎉 The release is available on: Your semantic-release bot 📦🚀 |
1 participant
Bumps
@exadev/eslint-configfrom 2.12.1 to 3.0.0 in the root and all three packages. No runtime code, behaviour or published API changes.3.0.0 makes
exadevConfigtake its options object alone, so each of the foureslint.config.tsfiles now spreadsexadevConfig()insidedefineConfigand lists its own blocks after it. Theconsistent-type-importsoverride has afilesglob because the shared config's plugins are now scoped to file globs.Going from 2.12.1 also pulls in the rules added across the 2.x line. What they flag is handled in the commits before the bump, each of which passes lint, typecheck and the unit tests on its own: JSON key order, test files renamed with a
unit,integrationore2esuffix (vitest globs and turbo inputs updated), and statement padding and comment placement.The few declarations that must keep their shape are exempted from the rule that flags them by files-scoped overrides in the package configs, each with its reason: the published
countsignature, the evaluator's positional parameters on the hot path, the async driver's sequential awaits, and the SQL fixtures' sequential seeding.Refs ExaDev/eslint-config#129