Skip to content

Commit 9462c15

Browse files
committed
feat(docs): add usecases and workflow documentation #81
Add usecases.md and workflow.md files to the docs folder. The usecases.md file contains information about the use cases of the application, while the workflow.md file explains the workflow design rules. The workflow.md file also includes a dataflow design with four steps: functional bootstrap, request transform/data validation, process IPC/RPC calling, and output transform/render. This documentation will provide a better understanding of the application's functionality and workflow.
1 parent b50b5df commit 9462c15

File tree

3 files changed

+33
-10
lines changed

3 files changed

+33
-10
lines changed

docs/usecases/usecases.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,19 @@
11
---
22
layout: default
3-
title: Usecases
3+
title: Workflow
44
nav_order: 6
55
has_children: true
6-
permalink: /usecases
6+
permalink: /workflow
77
---
88

9-
TODO: Usecases
9+
> AutoDev Workflow (#[81](https://github.com/unit-mesh/auto-dev/issues/81))
10+
11+
Dataflow design
12+
13+
1. Function bootstrap
14+
2. Request Transform / Data validation, IO Handing.
15+
3. Process IPC/RPC Calling
16+
4. Output Transform / Render
1017

1118
{: .no_toc }
1219

docs/workflow/usecases.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
layout: default
3+
title: Usecases
4+
nav_order: 7
5+
has_children: true
6+
permalink: /usecases
7+
---
8+
9+
TODO: Usecases
10+
11+
{: .no_toc }
12+

javascript/src/main/kotlin/cc/unitmesh/ide/javascript/flow/FrontendFlow.kt

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3,12 +3,15 @@ package cc.unitmesh.ide.javascript.flow
33
import cc.unitmesh.devti.flow.TaskFlow
44

55
/**
6+
* FrontendFlow is an interface that represents the flow of tasks in a frontend application.
7+
* It provides methods for retrieving routes, components, design system components, remote calls, and state management.
68
*
7-
* 1. Finding Function bootstrap, like the main function in java, ReactDom.render in React
8-
* 2. IO Handing
9-
* 3. Transform data, like State in React, Vuex in Vue
10-
* 4. Processing calling, like the fetch in React, the axios in Vue
11-
* 5. Output Transform, like the render in React, the template in Vue
9+
* Based on our workflow design rules: [Workflow](http://ide.unitmesh.cc/workflow)
10+
*
11+
* 1. Functional bootstrap
12+
* 2. Request Transform / Data validation, IO Handing.
13+
* 3. Process IPC/RPC Calling
14+
* 4. Output Transform / Render
1215
*/
1316
interface FrontendFlow : TaskFlow<String> {
1417
var userTask: String
@@ -26,7 +29,8 @@ interface FrontendFlow : TaskFlow<String> {
2629
fun getComponents(): List<DsComponent>
2730

2831
/**
29-
* Get the design system components, like the Ant Design in React, the Element in Vue
32+
* Get the design system components, like the Ant Design in React.
33+
* Which will load the design system components from the remote
3034
* @return list of design system components
3135
*/
3236
fun getDesignSystemComponents(): List<DsComponent>
@@ -38,7 +42,7 @@ interface FrontendFlow : TaskFlow<String> {
3842
fun sampleRemoteCall(): String
3943

4044
/**
41-
* Get the state management, like the Vuex in Vue, the Redux in React, maybe Empty
45+
* Get the state management as a sample, like the Vuex in Vue, the Redux in React, maybe Empty
4246
* @return list of state management
4347
*/
4448
fun sampleStateManagement(): String?

0 commit comments

Comments
 (0)