Repository navigation
v1.1.3
Patch Changes
-
#10
1c87c49Thanks @stevensacks! - FixgaiaLint.testingfiles glob and configureexpect-expectrules to recognizeexpect*helpers.Glob fix. The vitest block was scoped to
['*.test.ts?(x)', '*.stories.ts?(x)', 'test/**/*.ts?(x)']— the first two patterns lack the**/prefix needed to match nested paths in ESLint flat config, so none of the vitest, jest-dom, orimport-x/no-useless-path-segmentsrules fired on files likeapp/components/Button/tests/index.test.tsx. Verified viaeslint --print-configagainst a nested test:vitest/*andjest-dom/*rules were absent from the effective config; the no-useless-path rule resolved to severity 0 (off, inherited from base) instead of error. Siblingtesting-libraryblock was unaffected (already correctly scoped to['**/*.test.ts?(x)']).Helper-aware
expect-expect. Once the glob is fixed,vitest/expect-expect(severity error) starts flagging tests that delegate their assertion to a helper — e.g.await expectNoA11yViolations(container), where theexpect()call lives inside the helper. Same pattern surfaces forplaywright/expect-expectagainstexpectNoSeriousA11yViolations(page). Both rules now whitelist functions matching/^expect[A-Z]/, so anyexpect*helper following the project's naming convention satisfies the rule without per-test disable directives.Effect after upgrading:
pnpm lint --fixrewritesimport X from '../index'→import X from '..'for every component test, previously-silent vitest/jest-dom rule violations on nested tests start surfacing, and a11y/e2e helpers that internally assert no longer tripexpect-expect.