Keep verification screenshots out of the repository
Browser checks leave screenshots behind, and they had been accumulating in the same directory as the Försäkringskassan captures, which are reference material for the scraper and belong in the repository. The two are now separated by where they sit rather than by what they happen to be called: verification output goes in an ignored subdirectory, and the note saying so sits next to the layout it describes.
This commit is contained in:
@@ -6,6 +6,10 @@ __pycache__/
|
||||
graphify-out
|
||||
backend/debug
|
||||
|
||||
# Ephemeral browser-verification screenshots (the tracked captures/ files are
|
||||
# scraper reference material and stay tracked).
|
||||
/captures/verification/
|
||||
|
||||
# C extensions
|
||||
*.so
|
||||
|
||||
|
||||
@@ -97,6 +97,8 @@ frontend/ TypeScript · React 18.3 · Vite 5 · Vitest
|
||||
|
||||
**Data layer (frontend):** components consume `src/hooks/*`, which call `src/services/api.ts`. Components should not call `fetch`/the API client directly.
|
||||
|
||||
**Browser-verification screenshots:** ephemeral screenshots from verification runs go in `captures/verification/` (which is gitignored), while `captures/` itself holds tracked scraper reference material.
|
||||
|
||||
---
|
||||
|
||||
## CONVENTIONS
|
||||
|
||||
Reference in New Issue
Block a user