akanealw/Charon
1
0
Fork 0
Code Issues Pull Requests Actions 16 Packages Projects Releases Wiki Activity

feat: add ManualDNSChallenge component and related hooks for manual DNS challenge management

Browse Source 
- Implemented `useManualChallenge`, `useChallengePoll`, and `useManualChallengeMutations` hooks for managing manual DNS challenges.
- Created tests for the `useManualChallenge` hooks to ensure correct fetching and mutation behavior.
- Added `ManualDNSChallenge` component for displaying challenge details and actions.
- Developed end-to-end tests for the Manual DNS Provider feature, covering provider selection, challenge UI, and accessibility compliance.
- Included error handling tests for verification failures and network errors.
This commit is contained in:
GitHub Actions
2026-01-12 04:01:40 +00:00
parent a199dfd079
commit d7939bed70
132 changed files with 8680 additions and 878 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
.github/agents/Planning.agent.md vendored
View File

@@ -67,9 +67,12 @@ Your goal is to design the **User Experience** first, then engineer the **Backen
}
```
### 🕵️ Phase 1: QA & Security
### 🕵️ Phase 1: Playwright E2E Tests (Run First)
1. Build tests for coverage of perposed code additions and chages based on how the code SHOULD work
1. Run `npx playwright test --project=chromium` to verify app functions correctly
2. If tests fail, trace root cause through frontend → backend flow
3. Write/update Playwright tests for new features in `tests/*.spec.ts`
4. Build unit tests for coverage of proposed code additions and changes based on how the code SHOULD work
### 🏗️ Phase 2: Backend Implementation (Go)
@@ -89,15 +92,19 @@ Your goal is to design the **User Experience** first, then engineer the **Backen
### 🕵️ Phase 3: QA & Security
1. Edge Cases: {List specific scenarios to test}
2. **Coverage Tests (MANDATORY)**:
1. **Playwright E2E Tests (MANDATORY - Run First)**:
- Run `npx playwright test --project=chromium` from project root
- All E2E tests must pass BEFORE running unit tests
- If E2E fails, trace root cause and fix before proceeding
2. Edge Cases: {List specific scenarios to test}
3. **Coverage Tests (MANDATORY - After E2E passes)**:
- Backend: Run VS Code task "Test: Backend with Coverage" or execute `scripts/go-test-coverage.sh`
- Frontend: Run VS Code task "Test: Frontend with Coverage" or execute `scripts/frontend-test-coverage.sh`
- Minimum coverage: 85% for both backend and frontend
- **Critical**: These are in manual stage of pre-commit for performance. Agents MUST run them via VS Code tasks or scripts before marking tasks complete.
3. Security: Run CodeQL and Trivy scans. Triage and fix any new errors or warnings.
4. **Type Safety (Frontend)**: Run VS Code task "Lint: TypeScript Check" or execute `cd frontend && npm run type-check`
5. Linting: Run `pre-commit` hooks on all files and triage anything not auto-fixed.
4. Security: Run CodeQL and Trivy scans. Triage and fix any new errors or warnings.
5. **Type Safety (Frontend)**: Run VS Code task "Lint: TypeScript Check" or execute `cd frontend && npm run type-check`
6. Linting: Run `pre-commit` hooks on all files and triage anything not auto-fixed.
### 📚 Phase 4: Documentation