zhangjie
9de76adb48
feat: lint
|
hai 4 meses | |
|---|---|---|
| cypress | %!s(int64=2) %!d(string=hai) anos | |
| docs | %!s(int64=3) %!d(string=hai) anos | |
| public | %!s(int64=4) %!d(string=hai) anos | |
| src | hai 4 meses | |
| vetur | %!s(int64=4) %!d(string=hai) anos | |
| .editorconfig | %!s(int64=3) %!d(string=hai) anos | |
| .env.development | hai 4 meses | |
| .eslintrc.js | %!s(int64=2) %!d(string=hai) anos | |
| .gitignore | %!s(int64=2) %!d(string=hai) anos | |
| .npmrc | %!s(int64=2) %!d(string=hai) anos | |
| README.md | %!s(int64=3) %!d(string=hai) anos | |
| components.d.ts | hai 1 ano | |
| cypress.config.ts | %!s(int64=2) %!d(string=hai) anos | |
| index.html | %!s(int64=3) %!d(string=hai) anos | |
| package.json | hai 6 meses | |
| pnpm-lock.yaml | hai 4 meses | |
| postcss.config.js | %!s(int64=4) %!d(string=hai) anos | |
| prebuild.mjs | %!s(int64=2) %!d(string=hai) anos | |
| prettier.config.js | %!s(int64=3) %!d(string=hai) anos | |
| tailwind.config.js | %!s(int64=3) %!d(string=hai) anos | |
| tsconfig.json | %!s(int64=2) %!d(string=hai) anos | |
| vetur.config.js | %!s(int64=4) %!d(string=hai) anos | |
| vite.config.ts | hai 4 meses |
README.md
Vue 3 + Typescript + Vite
This template should help get you started developing with Vue 3 and Typescript in Vite.
Recommended IDE Setup
VSCode + Vetur. Make sure to enable vetur.experimental.templateInterpolationService in settings!
If Using <script setup>
<script setup> is a feature that is currently in RFC stage. To get proper IDE support for the syntax, use Volar instead of Vetur (and disable Vetur).
Type Support For .vue Imports in TS
Since TypeScript cannot handle type information for .vue imports, they are shimmed to be a generic Vue component type by default. In most cases this is fine if you don't really care about component prop types outside of templates. However, if you wish to get actual prop types in .vue imports (for example to get props validation when using manual h(...) calls), you can use the following:
If Using Volar
Run Volar: Switch TS Plugin on/off from VSCode command palette.
核心组件复用
主要分为：CommonMarkBody.vue 前端切片渲染的组件，凡是评卷任务类型的都可以复用它来渲染（包含轨迹）。
src/features/student/studentInspect/MarkBody.vue 整卷渲染的组件，凡是不用前端切分的试卷都可以复用它来渲染（包含轨迹）。
Reactivity 关联 CommonMarkBody.vue MarkBoardTrack.vue MarkBoardMouse.vue MarkBoardKeyBoard.vue MarkHistory.vue
以上组件的 reactivity 比较复杂，总结如下：
- currentTask 切换后，所有组件都得跟着变
- 轨迹模式下，
- 分数轨迹发生变化，MarkBoardTrack.vue 改变 store.removeScoreTracks ，CommonMarkBody.vue 监听 store.removeScoreTracks 改变 sliceImagesWithTrackList 的 trackList
- 特殊标记轨迹发生变化，SpecialTagModal.vue 改变 store.currentMarkResult.specialTagList ，CommonMarkBody.vue 监听 store.currentMarkResult.specialTagList 改变 sliceImagesWithTrackList 的 tagList
- 分数之间的关系，(理想设计)
- 来源: question.score 和 track.score, history.task.markerScore 评卷时不参与给分板的计算和显示
- 初始收集: markResult.scoreList markResult.trackList.score markResult.markerScore 要区分 0 分和 null
- 轨迹改变：track.score 动态计算 scoreList，再显示到给分板上（单题和总分自动计算），只有轨迹改变才去计算 scoreList 对应的题的分数，这样可以尽可能长时间的显示旧分数
- 普通改变：scoreList[index]的值
- 回评时普通模式评分的记录在轨迹模式下如何保持？先将 task 中的 question.score 转移到 markResult.scoreList，如果 trackList 有变化，则更新对应 scoreList，不然则保持原样。
- 优化
- markResult 放到 task 里面？ 回评清理它的 markResult . DONE!
- 使用 pinia . DONE!
watch 的层次(列出有外部影响的状态)：
- Top component watch currentTask 1.1 body watch special: track 1.1 openSide
- header watch setting / status
- history watch open , change currentTask
- body watch trackList, computed score? emit 'trackListChange'('add', questionIndex, trackList)/('removeLast', questionIndex)/('removeAll',questionIndex)
- markboard watch currentQuestion, normal mode -> change scoreList[index]