Skip to content

Validate all hooks trigger correctly #2

@grandcamel

Description

@grandcamel

Description

Verify all 4 hooks trigger at the right times during development.

Hooks to Validate

PreToolUse Hooks

  • security-crypto-warning - Should trigger when editing files in:

    • packages/pearpass-lib-vault-core/
    • Files containing sodium, crypto, encrypt, decrypt
  • security-secrets-check - Should trigger on:

    • git commit
    • git add

PostToolUse Hooks

  • quality-i18n-reminder - Should trigger after writing to:

    • src/components/**/*.jsx
    • src/containers/**/*.jsx
    • src/screens/**/*.jsx
  • quality-test-reminder - Should trigger after writing to:

    • src/components/**/index.js
    • src/hooks/use*.js
    • src/context/*.js

Test Method

  1. Open PearPass project with plugin installed
  2. Perform each trigger action
  3. Verify hook message appears

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions