mirror of https://github.com/affaan-m/everything-claude-code.git synced 2026-06-17 00:46:53 +08:00

z3tz3r0 5108b20954

feat(rules): add vue and nuxt rule sets (#2250 )

* feat(rules): add vue and nuxt rule sets

Add rules/vue/ and rules/nuxt/, each with the standard 5-file layout (coding-style, hooks, patterns, security, testing) that extends common/, following the Adding a New Language convention in rules/README.md.

Vue rules reference the frontend-patterns and vite-patterns skills. Nuxt rules reference the nuxt4-patterns and vite-patterns skills. Content is concise (1.5 to 4 KB per file) since rules load as always-on context.

* fix(rules): address PR review on vue and nuxt rule sets

- nuxt/coding-style: generalize the srcDir-override note (drop project-specific 'this repo' phrasing so it is correct for any Nuxt project).

- vue/hooks: add **/*.ts and **/*.tsx to paths so the lint/typecheck guidance loads when editing composables and stores.

- nuxt/hooks: add **/*.vue to paths (covers pages/layouts/components) and wrap nuxi typecheck in a timeout, mirroring web/hooks.md.

- nuxt/security: tighten the /security-review auto-trigger scope to external fetch, credential handling, and sensitive mutations, with examples.

- nuxt/testing: correct 'Vitest-only' to note built-in Playwright E2E, and drop the @nuxt/test-utils version pin.

- README: register vue and nuxt in the structure tree and install examples.

Skipped: 'X specific' -> 'X-specific' hyphenation (all existing rule sets use the unhyphenated form, changing only vue/nuxt would be inconsistent); repeating the 80%/TDD mandate in nuxt/testing (already inherited from common/testing.md).

2026-06-15 14:01:38 -04:00

2.0 KiB

Raw Blame History

paths

**/*.vue

Vue Testing

This file extends common/testing.md with Vue specific content.

Stack

Vitest (Vite-native runner) plus @vue/test-utils. create-vue scaffolds @vitejs/plugin-vue.
DOM environment via happy-dom or jsdom, set in vite.config.ts under test.environment.

Rendering and Async

mount for a full render. shallowMount to stub all child components.
trigger and setValue return promises, await them.
flushPromises flushes resolved promise handlers. nextTick settles the DOM after a state change.

What to Test

Test the public interface only: props, emitted events, slots, rendered output.
Do not assert private state or internal methods, and do not rely solely on snapshots.

Composables

Composables that use only reactivity APIs unit-test directly: call the function, assert on the returned refs.
Composables that use lifecycle hooks or inject must be tested through a host component.

Pinia

In components: createTestingPinia() from @pinia/testing, passed via global.plugins. Actions are stubbed by default, set stubActions: false to run them. createSpy: vi.fn is required under Vitest (no Jest globals).
In isolation: beforeEach(() => setActivePinia(createPinia())) gives a fresh store per test and prevents state leakage.

Mount Config

global.plugins, global.stubs (stubs Transition / TransitionGroup by default), global.mocks (e.g. $router), global.provide (for inject, Symbol keys supported).
RouterLinkStub stubs router-link without mounting a full router.

const wrapper = mount(AuctionCard, {
  props: { id: 1 },
  global: { plugins: [createTestingPinia({ createSpy: vi.fn })] },
})
await wrapper.find('button').trigger('click')
expect(wrapper.emitted('bid')).toBeTruthy()

Reference

ECC skills: frontend-patterns, vite-patterns.
Docs: https://test-utils.vuejs.org/api/ · https://pinia.vuejs.org/cookbook/testing.html · https://vitest.dev/

2.0 KiB Raw Blame History