Difficulty
Intermediate
Type
refactor, consistency, structure
Background
The current compilation trace shows components/nav.tsx importing through lib/api/index.ts, which in turn depends on lib/api/mock.ts. The mock implementation is therefore part of the application's API dependency boundary.
Problem
A large mock implementation exposed through the API layer can make consumers unnecessarily dependent on implementation details. Structural changes inside mock.ts can consequently break unrelated UI modules.
Expected outcome
Establish a clear API boundary so application components consume mock functionality through stable exports rather than depending on the internal organization of the mock implementation.
Suggested implementation
Review the exports in lib/api/index.ts and the symbols imported by components/nav.tsx. Consolidate mock-facing exports behind the API index and remove unnecessary direct exposure of internal mock structures. Preserve existing consumer behavior and names where they are already part of the application API.
Acceptance criteria
components/nav.tsx does not depend on internal mock implementation details.- Mock functionality required by the navigation is exported through the intended API boundary.
- Internal mock modules can be reorganized without requiring UI consumers to change imports.
- No unused mock exports are retained solely for compatibility unless they are actually consumed elsewhere.
- The application compiles successfully.
Likely affected files/directories
lib/api/index.tslib/api/mock.tscomponents/nav.tsx- Other files importing symbols directly from
lib/api/mock.ts, if present
Difficulty
Intermediate
Type
refactor, consistency, structure
Background
The current compilation trace shows
components/nav.tsximporting throughlib/api/index.ts, which in turn depends onlib/api/mock.ts. The mock implementation is therefore part of the application's API dependency boundary.Problem
A large mock implementation exposed through the API layer can make consumers unnecessarily dependent on implementation details. Structural changes inside
mock.tscan consequently break unrelated UI modules.Expected outcome
Establish a clear API boundary so application components consume mock functionality through stable exports rather than depending on the internal organization of the mock implementation.
Suggested implementation
Review the exports in
lib/api/index.tsand the symbols imported bycomponents/nav.tsx. Consolidate mock-facing exports behind the API index and remove unnecessary direct exposure of internal mock structures. Preserve existing consumer behavior and names where they are already part of the application API.Acceptance criteria
components/nav.tsxdoes not depend on internal mock implementation details.Likely affected files/directories
lib/api/index.tslib/api/mock.tscomponents/nav.tsxlib/api/mock.ts, if present