How krimtsev/portal-frontend works
This is a Vue-based partner portal with an administrative dashboard, user profiles, authentication, and partner-specific portal content. The typical flow is a user entering through routing and authentication, then working in a role-appropriate portal or dashboard view; views use API services to communicate with the backend. The sampled code verifies application setup, authentication state, dashboard routing, and HTTP behavior. Portal feature coverage comes from the file tree, so those internal links are marked unverified rather than asserted as observed calls.
Main entry points: index.ts Route registry · App.vue Layout and view host · dashboard Dashboard features · portal Partner services and content
Components 16
Application shell
- App bootstrap
src/main.ts - Layout and view host
src/App.vue - Route registry
src/router/index.ts - HTTP client
src/api/index.ts - Feature API modules
src/api/modules - Feature state
src/store
Identity and access
- Sign-in view
src/views/auth/auth-view.vue - Session state
src/store/auth/auth.ts - Authentication API
src/api/modules/auth/auth.ts
Dashboard operations
- Dashboard routes
src/router/dashboard/routes.ts - Dashboard features
src/views/dashboard
Partner portal
- Partner routes
src/router/portal/routes.ts - Partner services and content
src/views/portal - User profile and tickets
src/views/profile
Other components
- User
- Portal backend
Connections 22
- App bootstrap → Layout and view host: mounts
src/main.ts - App bootstrap → Route registry: installs
src/main.ts - User → Route registry: navigates
- Route registry → Layout and view host: provides route
- Layout and view host → Dashboard features: renders dashboard
- Layout and view host → Partner services and content: renders portal
- User → Sign-in view: signs in
- Sign-in view → HTTP client: uses API client
src/views/auth/auth-view.vue - Session state → Authentication API: calls
src/store/auth/auth.ts - Authentication API → HTTP client: uses
src/api/modules/auth/auth.ts - HTTP client → Portal backend: sends requests
src/api/index.ts - Dashboard routes → Dashboard features: routes to
src/router/dashboard/routes.ts - Route registry → Dashboard routes: registers
- Route registry → Partner routes: registers
- Partner routes → Partner services and content: routes to
- Route registry → User profile and tickets: routes to
- Dashboard features → Feature API modules: requests data
- Partner services and content → Feature API modules: requests data
- User profile and tickets → Feature API modules: requests data
- Feature API modules → HTTP client: uses client
src/api/modules/app/app.ts - Dashboard features → Feature state: uses feature state
- Partner services and content → Feature state: uses feature state