# art-design-to-ruoyi

**Repository Path**: wangqiang66/art-design-to-ruoyi

## Basic Information

- **Project Name**: art-design-to-ruoyi
- **Description**: No description available
- **Primary Language**: Unknown
- **License**: MIT
- **Default Branch**: main
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2026-03-10
- **Last Updated**: 2026-03-13

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

# TMS Web

Web3 financial operations and compliance admin platform for transaction workflows, wallet risk operations, customer lifecycle management, and internal back-office governance.

## Overview

This system is designed as a broader Web3 financial back-office platform.  
The current release implements part of the full target scope, with additional business modules planned in upcoming iterations.

## Business Scope and Module Status

### Currently Implemented

#### 1) Customer Onboarding

- Multi-stage review queues: `Initial Review`, `Secondary Review`, `Final Decision`
- Case handling actions: `Approve`, `Reject`, `RFI`, `Escalate`, `Return to L1`
- Structured review evidence: identity profile, digital evidence, supporting documents, audit trail

#### 2) Case Investigation (Web3 Transactions)

- Transaction-focused queues: `Initial Review`, `Secondary Review`, `Final Decision`
- Web3 fields and context: wallet address, transaction hash, asset/amount, counterparty, risk score
- Investigator actions: `Reject`, `RFI`, `Clear / Dismiss`, `Escalate Case`, `Regulatory Filing`, `Close Case`

#### 3) Platform Administration and Monitoring

- Dynamic route/menu loading and RBAC permission controls
- System administration: users, roles, menus, dictionaries, runtime config, notices
- Operational monitoring: operation logs, login logs, online users, cache, druid, server/job endpoints

### Planned (Not Yet Developed or Partially Under Development)

- Customer information management
- Financial reconciliation
- Additional wallet operations modules
- Extended reporting and operational analytics
- More domain-specific workflow modules for Web3 operations and finance controls

## Platform Capabilities

- Dynamic route/menu loading via backend menu API
- Role-based permission control for pages and actions
- Token-based authentication with request interceptors
- System management and monitoring modules for operations governance
- API fallback strategy: key workflow modules include mock fallback for resilient frontend development

## Technology Stack

- Frontend: Vue 3, TypeScript, Vite
- UI: Element Plus, Tailwind CSS 4
- State & Routing: Pinia, Vue Router
- Networking: Axios (custom request layer)
- Tooling: ESLint, Prettier, Stylelint, Husky, lint-staged, Commitizen

## Runtime Requirements

- Node.js `>= 20.19.0`
- pnpm `>= 8.8.0`

## Quick Start

```bash
pnpm install
pnpm dev
```

The local dev server runs on `VITE_PORT` (default: `3006`).

## Build and Preview

```bash
pnpm build
pnpm serve
```

## Common Scripts

```bash
pnpm dev                # start development server
pnpm build              # type-check + production build
pnpm serve              # preview production build
pnpm lint               # run eslint
pnpm fix                # auto-fix eslint issues
pnpm lint:prettier      # format code
pnpm lint:stylelint     # fix style issues
pnpm clean:dev          # cleanup script for development baseline
```

## Environment Variables

| Variable | Description | Example |
| --- | --- | --- |
| `VITE_VERSION` | App version injected at build time | `0.0.1` |
| `VITE_PORT` | Dev server port | `3006` |
| `VITE_BASE_URL` | Base public path for deployment | `/` |
| `VITE_API_PREFIX` | Frontend API prefix used by proxy | `/tms-api` |
| `VITE_API_PROXY_URL` | Proxy target for development backend | `http://vue.ruoyi.vip/prod-api` |
| `VITE_ACCESS_MODE` | Permission mode (`frontend` or `backend`) | `backend` |
| `VITE_WITH_CREDENTIALS` | Whether cross-origin requests send cookies | `false` |
| `VITE_OPEN_ROUTE_INFO` | Debug toggle for route information | `false` |
| `VITE_LOCK_ENCRYPT_KEY` | Lock-screen encryption key | `s3cur3k3y4adpro` |
| `VITE_APP_ENV` | Environment label | `development` / `production` |
| `VITE_DROP_CONSOLE` | Remove console output in build mode | `true` / `false` |

## API Integration Notes

- Development proxy rewrites requests from `VITE_API_PREFIX` to `VITE_API_PROXY_URL`.
- Workflow endpoints are domain-aware (for example: onboarding vs investigation).
- Several business APIs include mock fallback logic to keep pages usable when backend endpoints are unavailable.

## Project Structure

```text
src/
  api/                    # business APIs (workflow, onboarding, investigation, system, monitor)
  views/
    customer-onboarding/  # onboarding list/detail/review pages
    case-investigation/   # transaction investigation list/detail/review pages
    system/               # admin management pages
    monitor/              # operational monitoring pages
  router/                 # static + dynamic route handling
  store/                  # pinia stores
  utils/                  # http client, helpers, encryption, table helpers
  constants/              # workflow enums and option mappings
```

## License

[MIT](./LICENSE)

## Copyright

Copyright © 2026 Quantum Sailing Technology Limited. All rights reserved.

This software and its associated documentation are proprietary and confidential to Quantum Sailing Technology Limited.

Unauthorized use, copying, modification, distribution, disclosure, or reverse engineering of this software, in whole or in part, is strictly prohibited without prior written permission from Quantum Sailing Technology Limited.