How paulbraganza12/iban-validator works
Project type and purpose
• From the file tree and README, this is a full-stack IBAN-validation Single-Page Application (SPA) built with Create React App (TypeScript) on the frontend, accompanied by a backend (in the go/ directory or via Ruby Rake scripts) that actually performs the IBAN-validation logic.
• The UI offers input components (Validation and ValidationList), uses reusable hooks (useIban, useIbanValidation), and defines two service layers (ValidationViewModelService for transforming data for the view, and ValidationApiService for HTTP calls). Extensive testing is in place: Jest for unit tests and Cypress for end-to-end “journey” tests.
File structure
• Top level:
• Dot files (ESLint, Prettier, tool-versions, envrc) and package.json/Gemfile (Node & Ruby toolchain)
• public/ – static assets for CRA
• src/ – React components, hooks, services, styles, tests
• go/ – Go backend (presumed BFF/microservice)
• rake/ + Rakefile – Ruby-based build or orchestration scripts
• In src/ you see logical separation:
• components/ – presentational components
• hooks/ – domain-specific hooks (IBAN input, async validation)
• service/ – two layers: API client and ViewModel service
• __test__/unit/ – Jest unit tests exercising those services
• __test__/journey/ – Cypress tests driving the full stack (with fakes in support/arrangments/bff-responses.ts)
Detail without over-splitting
• Every distinct piece: components vs. hooks vs. services
• External dependencies (ESLint, Prettier, CI scripts) in a supporting-tools section