Keep explicit DTO, mapper, service, data model and provider layers throughout client code and shared packages.
Approach
Strengthen root and frontend instructions, document the dependency boundaries, and align auth stub responses with the existing KYC/wallet mapping structure.
Acceptance criteria
Architecture explicitly applies to web, mobile, shared packages and stubs.
Auth stub responses use DTOs and mappers with unchanged behavior.
Formatting, affected-package analysis and frontend tests pass; documented and delivered in a PR.
Notes
Based on workspace PR #29. No live backend integration or user-facing changes. Preserve existing contracts and simulated analytics.
Delivered in PR #31, branch architecture-30, based on workspace-28 / PR #29. Also aligned wallet profile DTO conversion. All 115 frontend tests, both affected package analyses, changed Dart formatting and diff checks pass. Scope and stack order recorded in docs/implementation.md. Not merged.
### Goal
Keep explicit DTO, mapper, service, data model and provider layers throughout client code and shared packages.
### Approach
Strengthen root and frontend instructions, document the dependency boundaries, and align auth stub responses with the existing KYC/wallet mapping structure.
### Acceptance criteria
- [x] Architecture explicitly applies to web, mobile, shared packages and stubs.
- [x] Services expose models, providers coordinate services, and UI uses provider state.
- [x] Auth stub responses use DTOs and mappers with unchanged behavior.
- [x] Formatting, affected-package analysis and frontend tests pass; documented and delivered in a PR.
### Notes
Based on workspace PR #29. No live backend integration or user-facing changes. Preserve existing contracts and simulated analytics.
Delivered in [PR #31](https://git.sendico.io/tech/sxchnge/pulls/31), branch architecture-30, based on workspace-28 / PR #29. Also aligned wallet profile DTO conversion. All 115 frontend tests, both affected package analyses, changed Dart formatting and diff checks pass. Scope and stack order recorded in docs/implementation.md. Not merged.
tech
added the frontend label 2026-09-12 10:07:31 +00:00
tech
self-assigned this 2026-09-12 10:07:31 +00:00
tech
added this to the SXCHNGE project 2026-09-12 10:07:31 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Goal
Keep explicit DTO, mapper, service, data model and provider layers throughout client code and shared packages.
Approach
Strengthen root and frontend instructions, document the dependency boundaries, and align auth stub responses with the existing KYC/wallet mapping structure.
Acceptance criteria
Notes
Based on workspace PR #29. No live backend integration or user-facing changes. Preserve existing contracts and simulated analytics.
Delivered in PR #31, branch architecture-30, based on workspace-28 / PR #29. Also aligned wallet profile DTO conversion. All 115 frontend tests, both affected package analyses, changed Dart formatting and diff checks pass. Scope and stack order recorded in docs/implementation.md. Not merged.