Skip to content

Commit 2a34003

Browse files
committed
[Fix][Engine UI] update the doc. How to use it
1 parent 93bd2ce commit 2a34003

File tree

1 file changed

+2
-32
lines changed
  • seatunnel-engine/seatunnel-engine-ui

1 file changed

+2
-32
lines changed

Diff for: seatunnel-engine/seatunnel-engine-ui/README.md

+2-32
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,5 @@
11
# seatunnel-engine-ui
22

3-
This template should help get you started developing with Vue 3 in Vite.
4-
5-
## Recommended IDE Setup
6-
7-
[VSCode](https://code.visualstudio.com/) + [Volar](https://marketplace.visualstudio.com/items?itemName=Vue.volar) (and disable Vetur).
8-
9-
## Type Support for `.vue` Imports in TS
10-
11-
TypeScript cannot handle type information for `.vue` imports by default, so we replace the `tsc` CLI with `vue-tsc` for type checking. In editors, we need [Volar](https://marketplace.visualstudio.com/items?itemName=Vue.volar) to make the TypeScript language service aware of `.vue` types.
12-
13-
## Customize configuration
14-
15-
See [Vite Configuration Reference](https://vitejs.dev/config/).
16-
173
## Project Setup
184

195
```sh
@@ -32,29 +18,13 @@ pnpm dev
3218
pnpm build
3319
```
3420

35-
### Run Unit Tests with [Vitest](https://vitest.dev/)
21+
### Run Unit Tests with [Vitest]
3622

3723
```sh
3824
pnpm test:unit
3925
```
4026

41-
### Run End-to-End Tests with [Cypress](https://www.cypress.io/)
42-
43-
```sh
44-
pnpm test:e2e:dev
45-
```
46-
47-
This runs the end-to-end tests against the Vite development server.
48-
It is much faster than the production build.
49-
50-
But it's still recommended to test the production build with `test:e2e` before deploying (e.g. in CI environments):
51-
52-
```sh
53-
pnpm build
54-
pnpm test:e2e
55-
```
56-
57-
### Lint with [ESLint](https://eslint.org/)
27+
### Lint with [ESLint]
5828

5929
```sh
6030
pnpm lint

0 commit comments

Comments
 (0)