Skip to content

feat: add admin users page (likec4)#1

Open
parse wants to merge 5 commits intomainfrom
test/frontend-bypasses-gateway
Open

feat: add admin users page (likec4)#1
parse wants to merge 5 commits intomainfrom
test/frontend-bypasses-gateway

Conversation

@parse
Copy link
Contributor

@parse parse commented Feb 24, 2026

Summary

  • Adds /admin/users route to the frontend that fetches directly from user-service:3001
  • This bypasses the api-gateway, introducing an architecture violation for testing erode's analyze command

Test plan

  • Run erode analyze against this PR to verify it detects the frontend → user-service violation

🤖 Generated with Claude Code

@erode-app erode-app deleted a comment from erode-app bot Feb 25, 2026
@erode-app erode-app deleted a comment from erode-app bot Feb 25, 2026
@erode-app erode-app deleted a comment from erode-app bot Feb 25, 2026
Add /admin/users route that fetches directly from user-service,
bypassing the api-gateway. This introduces an architecture violation
for testing erode's analyze command.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@parse parse force-pushed the test/frontend-bypasses-gateway branch from 1e3eed5 to 8254c79 Compare February 27, 2026 07:40
@parse parse changed the title feat: add admin users page feat: add admin users page (likec4) Feb 27, 2026
@erode-app erode-app deleted a comment from erode-app bot Feb 27, 2026
@erode-app
Copy link

erode-app bot commented Feb 27, 2026

Architectural Drift Analysis

Component: frontend (Web Frontend)

Selected from 5 candidates
  • frontend (Web Frontend)
  • api_gateway (API Gateway)
  • user_service (User Service)
  • product_service (Product Service)
  • database (Database)

Status: ⚠️ Issues detected

Detected Issues (1)

  • [HIGH] The frontend web application now makes a direct call to the user-service, bypassing the api_gateway. This is a clear architectural violation as the allowed dependencies (per the model) specify that frontend may only connect to the API Gateway (api_gateway) via https, not directly to user_service.
    • Source: packages/frontend/src/index.ts
    • Recommendation: Revert or guard this change; the frontend should only interact with user-service via the api_gateway to preserve architectural boundaries. Alternatively, update the model only if this is an intentional and sustainable architectural shift.

How to Resolve:
Adjust the architecture model to:

  • Include missing relationships between components
  • Revise component boundaries if code has been relocated
  • Record intentional architectural changes

Overview

This PR introduces a direct dependency from the frontend to the user-service, bypassing the mandated api_gateway boundary. This is a high-severity architectural violation and constitutes intentional drift for testing purposes, but should not be merged into production code or the architecture model.

Analysis details
AI Provider openai
Quick model (Stages 1, 2) gpt-4.1-mini
Deep model (Stage 3) gpt-4.1

Automated by erode

@erode-app erode-app locked and limited conversation to collaborators Mar 3, 2026
@erode-app erode-app unlocked this conversation Mar 3, 2026
@erode-app erode-app locked and limited conversation to collaborators Mar 3, 2026
@erode-app erode-app unlocked this conversation Mar 7, 2026
@erode-app erode-app locked and limited conversation to collaborators Mar 7, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant