feat:【ele】【crm】receivable 完成

This commit is contained in:
YunaiV
2025-11-18 13:13:20 +08:00
parent ffd74a749f
commit 07c3cb2f13
12 changed files with 32 additions and 111 deletions

View File

@@ -1,89 +0,0 @@
## Git Commit Message Convention
> This is adapted from [Angular's commit convention](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-angular).
#### TL;DR:
Messages must be matched by the following regex:
```js
/^(revert: )?(feat|fix|docs|style|refactor|perf|test|workflow|build|ci|chore|types|wip): .{1,50}/;
```
#### Examples
Appears under "Features" header, `dev` subheader:
```
feat(dev): add 'comments' option
```
Appears under "Bug Fixes" header, `dev` subheader, with a link to issue #28:
```
fix(dev): fix dev error
close #28
```
Appears under "Performance Improvements" header, and under "Breaking Changes" with the breaking change explanation:
```
perf(build): remove 'foo' option
BREAKING CHANGE: The 'foo' option has been removed.
```
The following commit and commit `667ecc1` do not appear in the changelog if they are under the same release. If not, the revert commit appears under the "Reverts" header.
```
revert: feat(compiler): add 'comments' option
This reverts commit 667ecc1654a317a13331b17617d973392f415f02.
```
### Full Message Format
A commit message consists of a **header**, **body** and **footer**. The header has a **type**, **scope** and **subject**:
```
<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>
```
The **header** is mandatory and the **scope** of the header is optional.
### Revert
If the commit reverts a previous commit, it should begin with `revert: `, followed by the header of the reverted commit. In the body, it should say: `This reverts commit <hash>.`, where the hash is the SHA of the commit being reverted.
### Type
If the prefix is `feat`, `fix` or `perf`, it will appear in the changelog. However, if there is any [BREAKING CHANGE](#footer), the commit will always appear in the changelog.
Other prefixes are up to your discretion. Suggested prefixes are `docs`, `chore`, `style`, `refactor`, and `test` for non-changelog related tasks.
### Scope
The scope could be anything specifying the place of the commit change. For example `dev`, `build`, `workflow`, `cli` etc...
### Subject
The subject contains a succinct description of the change:
- use the imperative, present tense: "change" not "changed" nor "changes"
- don't capitalize the first letter
- no dot (.) at the end
### Body
Just as in the **subject**, use the imperative, present tense: "change" not "changed" nor "changes". The body should include the motivation for the change and contrast this with previous behavior.
### Footer
The footer should contain any information about **Breaking Changes** and is also the place to reference GitHub issues that this commit **Closes**.
**Breaking Changes** should start with the word `BREAKING CHANGE:` with a space or two newlines. The rest of the commit message is then used for this.

View File

@@ -40,7 +40,6 @@ const permissionListRef = ref<InstanceType<typeof PermissionList>>(); // 团队
const [Descriptions] = useDescription({
bordered: false,
column: 4,
class: 'mx-4',
schema: useDetailSchema(),
});

View File

@@ -29,7 +29,7 @@ const [SystemDescriptions] = useDescription({
</script>
<template>
<div class="p-4">
<div>
<BaseDescriptions :data="receivable" />
<Divider />
<SystemDescriptions :data="receivable" />

View File

@@ -161,7 +161,7 @@ const [Grid, gridApi] = useVbenVxeGrid({
<FormModal @success="handleRefresh" />
<Grid>
<template toolbar-actions>
<template #toolbar-actions>
<Tabs class="w-full" @change="handleChangeSceneType">
<Tabs.TabPane tab="我负责的" key="1" />
<Tabs.TabPane tab="我参与的" key="2" />

View File

@@ -34,14 +34,11 @@ const receivablePlan = ref<CrmReceivablePlanApi.Plan>(
);
const logList = ref<SystemOperateLogApi.OperateLog[]>([]); // 操作日志
const permissionListRef = ref<InstanceType<typeof PermissionList>>(); // 团队成员列表 Ref
// 校验编辑权限
const validateWrite = () => permissionListRef.value?.validateWrite;
const validateWrite = () => permissionListRef.value?.validateWrite; // 校验编辑权限
const [Descriptions] = useDescription({
bordered: false,
column: 4,
class: 'mx-4',
schema: useDetailSchema(),
});

View File

@@ -29,7 +29,7 @@ const [SystemDescriptions] = useDescription({
</script>
<template>
<div class="p-4">
<div>
<BaseDescriptions :data="receivablePlan" />
<Divider />
<SystemDescriptions :data="receivablePlan" />

View File

@@ -28,7 +28,7 @@ const [SystemDescriptions] = useDescription({
</script>
<template>
<div class="p-4">
<div>
<BaseDescriptions :data="clue" />
<ElDivider />
<SystemDescriptions :data="clue" />

View File

@@ -34,14 +34,13 @@ const receivableId = ref(0); // 回款编号
const receivable = ref<CrmReceivableApi.Receivable>(
{} as CrmReceivableApi.Receivable,
); // 回款详情
const activeTabName = ref('1'); // 选中 Tab 名
const logList = ref<SystemOperateLogApi.OperateLog[]>([]); // 操作日志
const permissionListRef = ref<InstanceType<typeof PermissionList>>(); // 团队成员列表 Ref
const activeTabName = ref('1'); // 选中 Tab 名
const [Descriptions] = useDescription({
border: false,
column: 4,
class: 'mx-4',
schema: useDetailSchema(),
});

View File

@@ -15,7 +15,6 @@ const [BaseDescriptions] = useDescription({
title: '基本信息',
border: false,
column: 4,
class: 'mx-4',
schema: useDetailBaseSchema(),
});
@@ -23,13 +22,12 @@ const [SystemDescriptions] = useDescription({
title: '系统信息',
border: false,
column: 3,
class: 'mx-4',
schema: useDetailSystemSchema(),
});
</script>
<template>
<div class="p-4">
<div>
<BaseDescriptions :data="receivable" />
<ElDivider />
<SystemDescriptions :data="receivable" />

View File

@@ -8,7 +8,13 @@ import { useRouter } from 'vue-router';
import { DocAlert, Page, useVbenModal } from '@vben/common-ui';
import { downloadFileFromBlobPart } from '@vben/utils';
import { ElButton, ElLoading, ElMessage, ElTabPane, ElTabs } from 'element-plus';
import {
ElButton,
ElLoading,
ElMessage,
ElTabPane,
ElTabs,
} from 'element-plus';
import { ACTION_ICON, TableAction, useVbenVxeGrid } from '#/adapter/vxe-table';
import {
@@ -160,7 +166,11 @@ const [Grid, gridApi] = useVbenVxeGrid({
<FormModal @success="handleRefresh" />
<Grid>
<template #toolbar-actions>
<ElTabs v-model:model-value="sceneType" class="w-full" @tab-change="handleChangeSceneType">
<ElTabs
class="w-full"
@tab-change="handleChangeSceneType"
v-model:model-value="sceneType"
>
<ElTabPane label="我负责的" name="1" />
<ElTabPane label="我参与的" name="2" />
<ElTabPane label="下属负责的" name="3" />

View File

@@ -35,14 +35,11 @@ const receivablePlan = ref<CrmReceivablePlanApi.Plan>(
const activeTabName = ref('1'); // 选中 Tab 名
const logList = ref<SystemOperateLogApi.OperateLog[]>([]); // 操作日志
const permissionListRef = ref<InstanceType<typeof PermissionList>>(); // 团队成员列表 Ref
// 校验编辑权限
const validateWrite = () => permissionListRef.value?.validateWrite;
const validateWrite = () => permissionListRef.value?.validateWrite; // 校验编辑权限
const [Descriptions] = useDescription({
border: false,
column: 4,
class: 'mx-4',
schema: useDetailSchema(),
});

View File

@@ -8,7 +8,13 @@ import { useRouter } from 'vue-router';
import { DocAlert, Page, useVbenModal } from '@vben/common-ui';
import { downloadFileFromBlobPart } from '@vben/utils';
import { ElButton, ElLoading, ElMessage, ElTabPane, ElTabs } from 'element-plus';
import {
ElButton,
ElLoading,
ElMessage,
ElTabPane,
ElTabs,
} from 'element-plus';
import { ACTION_ICON, TableAction, useVbenVxeGrid } from '#/adapter/vxe-table';
import {
@@ -144,7 +150,11 @@ const [Grid, gridApi] = useVbenVxeGrid({
<ReceivableFormModal @success="handleRefresh" />
<Grid>
<template #toolbar-actions>
<ElTabs v-model:model-value="sceneType" class="w-full" @tab-change="handleChangeSceneType">
<ElTabs
class="w-full"
@tab-change="handleChangeSceneType"
v-model:model-value="sceneType"
>
<ElTabPane label="我负责的" name="1" />
<ElTabPane label="下属负责的" name="3" />
</ElTabs>