rhjy-ui 0.2.6 → 0.2.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +262 -261
- package/dist/data-center/index.cjs +1 -1
- package/dist/data-center/index.js +192 -189
- package/dist/data-center/types.d.ts +1 -0
- package/dist/style.css +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,261 +1,262 @@
|
|
|
1
|
-
# rhjy-ui
|
|
2
|
-
|
|
3
|
-
`rhjy-ui` is a Vue 3 and Element Plus business UI component library. The first release contains a configurable data-center suite for displaying asynchronous import, export, generation and other background tasks.
|
|
4
|
-
|
|
5
|
-
## Install
|
|
6
|
-
|
|
7
|
-
```bash
|
|
8
|
-
pnpm add rhjy-ui vue element-plus @element-plus/icons-vue
|
|
9
|
-
```
|
|
10
|
-
|
|
11
|
-
Import the package stylesheet once in the application entrypoint:
|
|
12
|
-
|
|
13
|
-
```ts
|
|
14
|
-
import 'rhjy-ui/style.css'
|
|
15
|
-
```
|
|
16
|
-
|
|
17
|
-
## Responsive Info Grid
|
|
18
|
-
|
|
19
|
-
Responsive Info Grid arranges title-content pairs in a configurable grid and switches column counts at the 1200px and 768px breakpoints.
|
|
20
|
-
|
|
21
|
-
```vue
|
|
22
|
-
<script setup lang="ts">
|
|
23
|
-
import {
|
|
24
|
-
RhResponsiveInfoGrid,
|
|
25
|
-
RhResponsiveInfoGridItem,
|
|
26
|
-
} from 'rhjy-ui'
|
|
27
|
-
</script>
|
|
28
|
-
|
|
29
|
-
<template>
|
|
30
|
-
<RhResponsiveInfoGrid>
|
|
31
|
-
<RhResponsiveInfoGridItem title="Project: " content="Smart Campus" />
|
|
32
|
-
<RhResponsiveInfoGridItem title="Owner: " content="Operations Team" />
|
|
33
|
-
<RhResponsiveInfoGridItem title="Devices: " :content="128" />
|
|
34
|
-
<RhResponsiveInfoGridItem title="Summary: " content="All systems operational" :span="2" />
|
|
35
|
-
</RhResponsiveInfoGrid>
|
|
36
|
-
</template>
|
|
37
|
-
```
|
|
38
|
-
|
|
39
|
-
See the [Responsive Info Grid component README](https://unpkg.com/rhjy-ui@0.2.2/src/responsive-info-grid/README.md) for subpath imports, the complete props and slots reference, responsive behavior, and more examples.
|
|
40
|
-
|
|
41
|
-
## Data center panel
|
|
42
|
-
|
|
43
|
-
`rhjy-ui` never receives an API URL. Each application supplies a `loadTasks` function and converts its own response into the standard task model.
|
|
44
|
-
|
|
45
|
-
```vue
|
|
46
|
-
<script setup lang="ts">
|
|
47
|
-
import { RhDataCenter } from 'rhjy-ui'
|
|
48
|
-
import type {
|
|
49
|
-
RhDataCenterCategory,
|
|
50
|
-
RhDataCenterLoadTasks,
|
|
51
|
-
} from 'rhjy-ui/data-center'
|
|
52
|
-
|
|
53
|
-
const categories: RhDataCenterCategory[] = [
|
|
54
|
-
{ key: 'all', label: '全部任务' },
|
|
55
|
-
{ key: 'generate', label: '数据生成' },
|
|
56
|
-
{ key: 'import', label: '数据导入' },
|
|
57
|
-
{ key: 'export', label: '数据导出' },
|
|
58
|
-
]
|
|
59
|
-
|
|
60
|
-
const loadTasks: RhDataCenterLoadTasks = async ({ category }) => {
|
|
61
|
-
const response = await requestTaskList({
|
|
62
|
-
taskType: category.key === 'all' ? undefined : category.key,
|
|
63
|
-
})
|
|
64
|
-
|
|
65
|
-
return {
|
|
66
|
-
items: response.list,
|
|
67
|
-
total: response.total,
|
|
68
|
-
}
|
|
69
|
-
}
|
|
70
|
-
|
|
71
|
-
const handleTaskAction = ({ action, task }) => {
|
|
72
|
-
if (action === 'download') {
|
|
73
|
-
window.open(task.raw.fileUrl)
|
|
74
|
-
}
|
|
75
|
-
}
|
|
76
|
-
</script>
|
|
77
|
-
|
|
78
|
-
<template>
|
|
79
|
-
<RhDataCenter
|
|
80
|
-
:categories="categories"
|
|
81
|
-
:load-tasks="loadTasks"
|
|
82
|
-
sidebar-width="160px"
|
|
83
|
-
@task-action="handleTaskAction"
|
|
84
|
-
/>
|
|
85
|
-
</template>
|
|
86
|
-
```
|
|
87
|
-
|
|
88
|
-
The “全部任务” rule is application-owned. It may omit `taskType`, pass a fixed value, or combine multiple requests without changing the component.
|
|
89
|
-
|
|
90
|
-
### Reuse the business adapter
|
|
91
|
-
|
|
92
|
-
When multiple applications use the same data-center protocol, use `createRhDataCenterAdapter` to share response conversion, status messages, sorting, counts, and default download actions. The application still injects its own API functions; the package never receives an API URL.
|
|
93
|
-
|
|
94
|
-
```ts
|
|
95
|
-
import {
|
|
96
|
-
createRhDataCenterAdapter,
|
|
97
|
-
type RhDataCenterCategory,
|
|
98
|
-
} from 'rhjy-ui/data-center'
|
|
99
|
-
import { clickDownloadBtByTaskId, getMyTaskList } from '@/services/dataCenter'
|
|
100
|
-
|
|
101
|
-
const categories: RhDataCenterCategory[] = [
|
|
102
|
-
{ key: 'all', label: '全部任务', query: { taskType: 0 } },
|
|
103
|
-
{ key: 2, label: '数据导入', query: { taskType: 2 } },
|
|
104
|
-
{ key: 3, label: '数据导出', query: { taskType: 3 } },
|
|
105
|
-
]
|
|
106
|
-
|
|
107
|
-
const { loadTasks, handleTaskAction } = createRhDataCenterAdapter({
|
|
108
|
-
api: {
|
|
109
|
-
getTaskList: getMyTaskList,
|
|
110
|
-
downloadTask: ({ taskId }) => clickDownloadBtByTaskId({ taskId }),
|
|
111
|
-
},
|
|
112
|
-
categories,
|
|
113
|
-
taskKind: { import: [2], export: [3] },
|
|
114
|
-
|
|
115
|
-
|
|
116
|
-
|
|
117
|
-
|
|
118
|
-
|
|
119
|
-
|
|
120
|
-
|
|
121
|
-
|
|
122
|
-
|
|
123
|
-
|
|
124
|
-
|
|
125
|
-
|
|
126
|
-
:
|
|
127
|
-
:
|
|
128
|
-
:category-
|
|
129
|
-
|
|
130
|
-
|
|
131
|
-
|
|
132
|
-
|
|
133
|
-
|
|
134
|
-
|
|
135
|
-
|
|
136
|
-
|
|
137
|
-
|
|
138
|
-
|
|
139
|
-
|
|
140
|
-
|
|
141
|
-
|
|
142
|
-
|
|
143
|
-
|
|
144
|
-
|
|
145
|
-
|
|
146
|
-
|
|
147
|
-
|
|
148
|
-
|
|
149
|
-
|
|
150
|
-
|
|
151
|
-
|
|
152
|
-
|
|
153
|
-
})
|
|
154
|
-
|
|
155
|
-
|
|
156
|
-
|
|
157
|
-
|
|
158
|
-
|
|
159
|
-
|
|
160
|
-
|
|
161
|
-
|
|
162
|
-
|
|
163
|
-
:
|
|
164
|
-
|
|
165
|
-
|
|
166
|
-
|
|
167
|
-
|
|
168
|
-
|
|
169
|
-
|
|
170
|
-
|
|
171
|
-
|
|
172
|
-
|
|
173
|
-
|
|
174
|
-
|
|
175
|
-
|
|
176
|
-
|
|
177
|
-
|
|
178
|
-
|
|
179
|
-
|
|
180
|
-
|
|
181
|
-
|
|
182
|
-
|
|
183
|
-
|
|
184
|
-
|
|
185
|
-
|
|
186
|
-
}
|
|
187
|
-
|
|
188
|
-
|
|
189
|
-
|
|
190
|
-
|
|
191
|
-
|
|
192
|
-
|
|
193
|
-
|
|
194
|
-
|
|
195
|
-
|
|
196
|
-
|
|
197
|
-
|
|
198
|
-
|
|
199
|
-
|
|
200
|
-
|
|
201
|
-
|
|
202
|
-
|
|
203
|
-
|
|
204
|
-
|
|
205
|
-
|
|
206
|
-
|
|
207
|
-
|
|
208
|
-
|
|
209
|
-
|
|
210
|
-
|
|
211
|
-
--rh-ui-data-center-
|
|
212
|
-
--rh-ui-data-center-panel-
|
|
213
|
-
|
|
214
|
-
|
|
215
|
-
|
|
216
|
-
|
|
217
|
-
|
|
218
|
-
|
|
219
|
-
|
|
220
|
-
|
|
221
|
-
|
|
222
|
-
|
|
223
|
-
|
|
224
|
-
|
|
225
|
-
|
|
226
|
-
|
|
227
|
-
|
|
228
|
-
|
|
229
|
-
|
|
230
|
-
|
|
231
|
-
|
|
232
|
-
|
|
233
|
-
|
|
234
|
-
|
|
235
|
-
|
|
236
|
-
|
|
237
|
-
|
|
238
|
-
|
|
239
|
-
|
|
240
|
-
|
|
241
|
-
|
|
242
|
-
|
|
243
|
-
|
|
244
|
-
|
|
245
|
-
|
|
246
|
-
|
|
247
|
-
npm
|
|
248
|
-
|
|
249
|
-
|
|
250
|
-
|
|
251
|
-
|
|
252
|
-
|
|
253
|
-
|
|
254
|
-
|
|
255
|
-
|
|
256
|
-
|
|
257
|
-
|
|
258
|
-
|
|
259
|
-
|
|
260
|
-
|
|
261
|
-
|
|
1
|
+
# rhjy-ui
|
|
2
|
+
|
|
3
|
+
`rhjy-ui` is a Vue 3 and Element Plus business UI component library. The first release contains a configurable data-center suite for displaying asynchronous import, export, generation and other background tasks.
|
|
4
|
+
|
|
5
|
+
## Install
|
|
6
|
+
|
|
7
|
+
```bash
|
|
8
|
+
pnpm add rhjy-ui vue element-plus @element-plus/icons-vue
|
|
9
|
+
```
|
|
10
|
+
|
|
11
|
+
Import the package stylesheet once in the application entrypoint:
|
|
12
|
+
|
|
13
|
+
```ts
|
|
14
|
+
import 'rhjy-ui/style.css'
|
|
15
|
+
```
|
|
16
|
+
|
|
17
|
+
## Responsive Info Grid
|
|
18
|
+
|
|
19
|
+
Responsive Info Grid arranges title-content pairs in a configurable grid and switches column counts at the 1200px and 768px breakpoints.
|
|
20
|
+
|
|
21
|
+
```vue
|
|
22
|
+
<script setup lang="ts">
|
|
23
|
+
import {
|
|
24
|
+
RhResponsiveInfoGrid,
|
|
25
|
+
RhResponsiveInfoGridItem,
|
|
26
|
+
} from 'rhjy-ui'
|
|
27
|
+
</script>
|
|
28
|
+
|
|
29
|
+
<template>
|
|
30
|
+
<RhResponsiveInfoGrid>
|
|
31
|
+
<RhResponsiveInfoGridItem title="Project: " content="Smart Campus" />
|
|
32
|
+
<RhResponsiveInfoGridItem title="Owner: " content="Operations Team" />
|
|
33
|
+
<RhResponsiveInfoGridItem title="Devices: " :content="128" />
|
|
34
|
+
<RhResponsiveInfoGridItem title="Summary: " content="All systems operational" :span="2" />
|
|
35
|
+
</RhResponsiveInfoGrid>
|
|
36
|
+
</template>
|
|
37
|
+
```
|
|
38
|
+
|
|
39
|
+
See the [Responsive Info Grid component README](https://unpkg.com/rhjy-ui@0.2.2/src/responsive-info-grid/README.md) for subpath imports, the complete props and slots reference, responsive behavior, and more examples.
|
|
40
|
+
|
|
41
|
+
## Data center panel
|
|
42
|
+
|
|
43
|
+
`rhjy-ui` never receives an API URL. Each application supplies a `loadTasks` function and converts its own response into the standard task model.
|
|
44
|
+
|
|
45
|
+
```vue
|
|
46
|
+
<script setup lang="ts">
|
|
47
|
+
import { RhDataCenter } from 'rhjy-ui'
|
|
48
|
+
import type {
|
|
49
|
+
RhDataCenterCategory,
|
|
50
|
+
RhDataCenterLoadTasks,
|
|
51
|
+
} from 'rhjy-ui/data-center'
|
|
52
|
+
|
|
53
|
+
const categories: RhDataCenterCategory[] = [
|
|
54
|
+
{ key: 'all', label: '全部任务' },
|
|
55
|
+
{ key: 'generate', label: '数据生成' },
|
|
56
|
+
{ key: 'import', label: '数据导入' },
|
|
57
|
+
{ key: 'export', label: '数据导出' },
|
|
58
|
+
]
|
|
59
|
+
|
|
60
|
+
const loadTasks: RhDataCenterLoadTasks = async ({ category }) => {
|
|
61
|
+
const response = await requestTaskList({
|
|
62
|
+
taskType: category.key === 'all' ? undefined : category.key,
|
|
63
|
+
})
|
|
64
|
+
|
|
65
|
+
return {
|
|
66
|
+
items: response.list,
|
|
67
|
+
total: response.total,
|
|
68
|
+
}
|
|
69
|
+
}
|
|
70
|
+
|
|
71
|
+
const handleTaskAction = ({ action, task }) => {
|
|
72
|
+
if (action === 'download') {
|
|
73
|
+
window.open(task.raw.fileUrl)
|
|
74
|
+
}
|
|
75
|
+
}
|
|
76
|
+
</script>
|
|
77
|
+
|
|
78
|
+
<template>
|
|
79
|
+
<RhDataCenter
|
|
80
|
+
:categories="categories"
|
|
81
|
+
:load-tasks="loadTasks"
|
|
82
|
+
sidebar-width="160px"
|
|
83
|
+
@task-action="handleTaskAction"
|
|
84
|
+
/>
|
|
85
|
+
</template>
|
|
86
|
+
```
|
|
87
|
+
|
|
88
|
+
The “全部任务” rule is application-owned. It may omit `taskType`, pass a fixed value, or combine multiple requests without changing the component.
|
|
89
|
+
|
|
90
|
+
### Reuse the business adapter
|
|
91
|
+
|
|
92
|
+
When multiple applications use the same data-center protocol, use `createRhDataCenterAdapter` to share response conversion, status messages, sorting, counts, and default download actions. The application still injects its own API functions; the package never receives an API URL.
|
|
93
|
+
|
|
94
|
+
```ts
|
|
95
|
+
import {
|
|
96
|
+
createRhDataCenterAdapter,
|
|
97
|
+
type RhDataCenterCategory,
|
|
98
|
+
} from 'rhjy-ui/data-center'
|
|
99
|
+
import { clickDownloadBtByTaskId, getMyTaskList } from '@/services/dataCenter'
|
|
100
|
+
|
|
101
|
+
const categories: RhDataCenterCategory[] = [
|
|
102
|
+
{ key: 'all', label: '全部任务', query: { taskType: 0 } },
|
|
103
|
+
{ key: 2, label: '数据导入', query: { taskType: 2 } },
|
|
104
|
+
{ key: 3, label: '数据导出', query: { taskType: 3 } },
|
|
105
|
+
]
|
|
106
|
+
|
|
107
|
+
const { loadTasks, handleTaskAction } = createRhDataCenterAdapter({
|
|
108
|
+
api: {
|
|
109
|
+
getTaskList: getMyTaskList,
|
|
110
|
+
downloadTask: ({ taskId }) => clickDownloadBtByTaskId({ taskId }),
|
|
111
|
+
},
|
|
112
|
+
categories,
|
|
113
|
+
taskKind: { import: [2], export: [3] },
|
|
114
|
+
completedDownloadKinds: ['other'],
|
|
115
|
+
})
|
|
116
|
+
```
|
|
117
|
+
|
|
118
|
+
The adapter provides default task actions for completed exports, import failure records, and failed tasks. Use `completedDownloadKinds` when another task kind should show a file download action after completion and its raw task contains `fileUrl`. Use `parseResponse` when the application response wrapper or success rule differs. Use `mapTask` or `resolveActions` for an application-specific field or operation without changing the shared adapter. `RhDataCenter` remains responsible for polling; the adapter handles one query and one task action at a time.
|
|
119
|
+
|
|
120
|
+
Use `sidebar-width` with a number or CSS size string to adjust the data type panel width. Its default value is `124px`.
|
|
121
|
+
|
|
122
|
+
Category counts are optional and application-owned. Set `show-category-count` to `false` to hide every category count, or pass `category-counts` to display values before individual categories are loaded:
|
|
123
|
+
|
|
124
|
+
```vue
|
|
125
|
+
<RhDataCenter
|
|
126
|
+
:categories="categories"
|
|
127
|
+
:load-tasks="loadTasks"
|
|
128
|
+
:show-category-count="true"
|
|
129
|
+
:category-counts="{ all: 20, generate: 8, import: 4, export: 8 }"
|
|
130
|
+
/>
|
|
131
|
+
```
|
|
132
|
+
|
|
133
|
+
When counts are enabled, the component uses `categoryCounts`, then a loaded result's `counts`, and finally the category result's `total`.
|
|
134
|
+
|
|
135
|
+
When the backend provides a separate count endpoint, configure it on the shared adapter. The count request runs in parallel with each task-list refresh, so the sidebar stays synchronized with polling without moving API details into `RhDataCenter`:
|
|
136
|
+
|
|
137
|
+
```ts
|
|
138
|
+
const { loadTasks, handleTaskAction } = createRhDataCenterAdapter<
|
|
139
|
+
RawTask,
|
|
140
|
+
TaskQuery,
|
|
141
|
+
TaskListResponse,
|
|
142
|
+
TaskCountResponse
|
|
143
|
+
>({
|
|
144
|
+
api: {
|
|
145
|
+
getTaskList: requestTaskList,
|
|
146
|
+
getTaskCounts: () => requestTaskCounts({ taskType: 0 }),
|
|
147
|
+
},
|
|
148
|
+
categories,
|
|
149
|
+
parseResponse: (response) => response.data.list,
|
|
150
|
+
parseCounts: (response) => ({
|
|
151
|
+
all: response.data.totalTaskCount,
|
|
152
|
+
import: response.data.taskCountList.find((item) => item.taskType === 2)?.taskCount ?? 0,
|
|
153
|
+
}),
|
|
154
|
+
})
|
|
155
|
+
```
|
|
156
|
+
|
|
157
|
+
`parseCounts` converts the shared backend response into category keys. If the count request or parser fails, the adapter keeps the task list available and falls back to `resolveCounts` or the loaded result totals.
|
|
158
|
+
|
|
159
|
+
Task tags read `raw.taskTypeName` by default. When an API uses another field name, pass `task-tag-field` without changing the task adapter:
|
|
160
|
+
|
|
161
|
+
```vue
|
|
162
|
+
<RhDataCenter
|
|
163
|
+
:categories="categories"
|
|
164
|
+
:load-tasks="loadTasks"
|
|
165
|
+
task-tag-field="taskTypeName"
|
|
166
|
+
/>
|
|
167
|
+
```
|
|
168
|
+
|
|
169
|
+
## Task tip flow
|
|
170
|
+
|
|
171
|
+
Use `useRhDataCenter` after a page successfully creates a background task:
|
|
172
|
+
|
|
173
|
+
```vue
|
|
174
|
+
<script setup lang="ts">
|
|
175
|
+
import { RhDataCenterTip, useRhDataCenter } from 'rhjy-ui'
|
|
176
|
+
|
|
177
|
+
const { tipVisible, tipConfig, showTip } = useRhDataCenter()
|
|
178
|
+
|
|
179
|
+
const startExport = async () => {
|
|
180
|
+
const result = await createExportTask()
|
|
181
|
+
showTip({
|
|
182
|
+
type: 'export',
|
|
183
|
+
minutes: Number(result.minutes),
|
|
184
|
+
title: '导出文件生成中,大概需要',
|
|
185
|
+
content: '现在你可关闭弹框,去做其他事情了。',
|
|
186
|
+
})
|
|
187
|
+
}
|
|
188
|
+
</script>
|
|
189
|
+
|
|
190
|
+
<template>
|
|
191
|
+
<RhDataCenterTip v-model="tipVisible" v-bind="tipConfig" />
|
|
192
|
+
</template>
|
|
193
|
+
```
|
|
194
|
+
|
|
195
|
+
`RhDataCenterTip` 默认使用简化引导动画;需要使用带数据处理中心图片、手势和方向切换的引导时,可传入 `guideVariant="normal"` 或 `guideVariant="super"`。
|
|
196
|
+
|
|
197
|
+
## Standard task model
|
|
198
|
+
|
|
199
|
+
The adapter returns `id`, `categoryKey`, `title`, `createdAt`, `progress`, and one of `waiting`, `processing`, `success`, or `failed`. Optional `tag`, `message`, `actions`, and `raw` provide display and application action context.
|
|
200
|
+
|
|
201
|
+
For completed tasks with rejected records, pass the normalized `failCount` field. The task item keeps the completed progress bar, shows `失败记录(xx条)` in red, and hides the normal completion message when the count is zero. The application still supplies the failure-record action and handles its download event.
|
|
202
|
+
|
|
203
|
+
For processing tasks, pass `taskSeconds` to show `总时长约X分XX秒` instead of the default processing message. If `taskSeconds` is omitted, the provided `message` is displayed.
|
|
204
|
+
|
|
205
|
+
## Styling
|
|
206
|
+
|
|
207
|
+
Override CSS variables at the application root when needed:
|
|
208
|
+
|
|
209
|
+
```css
|
|
210
|
+
:root {
|
|
211
|
+
--rh-ui-data-center-primary: #00828a;
|
|
212
|
+
--rh-ui-data-center-panel-width: 606px;
|
|
213
|
+
--rh-ui-data-center-panel-height: 500px;
|
|
214
|
+
}
|
|
215
|
+
```
|
|
216
|
+
|
|
217
|
+
## Build and publish
|
|
218
|
+
|
|
219
|
+
After changing the source code or component assets, run the package script in the `rh-ui` directory to regenerate `dist`:
|
|
220
|
+
|
|
221
|
+
```bash
|
|
222
|
+
cd D:\workfile\sass-workspace\packages\rh-ui
|
|
223
|
+
npm run package
|
|
224
|
+
```
|
|
225
|
+
|
|
226
|
+
The workspace equivalent is:
|
|
227
|
+
|
|
228
|
+
```bash
|
|
229
|
+
pnpm --filter rhjy-ui package
|
|
230
|
+
```
|
|
231
|
+
|
|
232
|
+
Before publishing, increment the package version without creating a Git tag:
|
|
233
|
+
|
|
234
|
+
```bash
|
|
235
|
+
npm run version:patch
|
|
236
|
+
```
|
|
237
|
+
|
|
238
|
+
Use `npm run version:minor` only for a backward-compatible feature release. You can inspect the files that will be published with:
|
|
239
|
+
|
|
240
|
+
```bash
|
|
241
|
+
npm pack --dry-run
|
|
242
|
+
```
|
|
243
|
+
|
|
244
|
+
After confirming the tarball contents, publish the public package:
|
|
245
|
+
|
|
246
|
+
```bash
|
|
247
|
+
npm login --registry=https://registry.npmjs.org --auth-type=web
|
|
248
|
+
npm publish --access public --registry=https://registry.npmjs.org
|
|
249
|
+
```
|
|
250
|
+
|
|
251
|
+
If the account uses two-factor authentication, npm opens the browser authentication flow. After publishing, synchronize the school admin project from this package directory:
|
|
252
|
+
|
|
253
|
+
```bash
|
|
254
|
+
cd D:\workfile\sass-workspace\packages\rh-ui
|
|
255
|
+
npm run sync:wise-school-admin
|
|
256
|
+
```
|
|
257
|
+
|
|
258
|
+
The script installs the latest public `rhjy-ui` release with an exact version and synchronizes `D:\workfile\wise-school-admin\package.json` and `package-lock.json`. It is intended for the fixed local workspace path; add another explicit `sync:<project>` script when a new application needs this workflow.
|
|
259
|
+
|
|
260
|
+
## Releases
|
|
261
|
+
|
|
262
|
+
The package is published with compiled `dist` output. Consumers should use an explicit version such as `rhjy-ui@0.2.2`; application-specific API adapters remain in the consuming project.
|