kate522andClaude Opus 5
dbb7de41e9
The old 售后 flow was an order-refund appendage: tickets were hard-bound to an order number, users could only file them from 「我的订单」against a paid order, and the admin action bottomed out at 「标记订单已退款」. It could not carry account questions or feature requests that have nothing to do with an order. Replace it with a general ticket system modelled on 魔方财务云's idcsmart_ticket: title + department + description are required, linking an order is optional (user's own paid orders only). Add departments, custom statuses, preset replies and internal admin notes as four configuration surfaces. Conversation history moves off the ticket row's JSON log into dedicated ticket_reply rows, which unlocks quoted replies. Front end gets a 工单中心 panel under 我的服务; back end moves from 支付中心 → 售后服务 to users.php → 工单管理. Per CLAUDE.md's rewrite-over-compatibility rule: drop the old table, build new ones, delete the old code. No dual paths, no data migration. The upstream plugin's upstream/downstream delivery and internal-ticket conversion are deliberately left out — both are multi-provider platform concerns with no meaning on a single WordPress site. Data: order_aftersale becomes six aksrt_ticket* tables (ticket, ticket_reply, ticket_status, ticket_type, ticket_prereply, ticket_note). SCHEMA_VERSION 2.6.0 -> 3.0.0. Status and department seeds are idempotent; the default status 「待接单」is flagged as non-editable. Domain: new src/Ticket/ (13 files, all under 460 lines). Attachments reuse UserController::rest_upload_comment_image with a ticket-specific permission callback, mirroring the existing /report/upload-image route rather than growing a second upload path. Notifications go through AKSRT\Messages\Message::send() and deep-link to the right surface; email/SMS stay out of scope since the theme's mail and SMS stacks are separate implementations. Refund gate opens up: marking an order refunded no longer requires an in-flight ticket, only that the order is paid. Also generalise a hardcoded special case in tools/audit-admin-contracts.php — schema domain inference now reads the parent directory instead of matching "PostList" by name, so new leaf schema files need no per-name exception. Verification: php tools/audit-admin-contracts.php exit 0, errors=0 node --test (widget-system + admin) 664 pass / 0 fail php -l over all new/changed files clean node --check over all JS clean npm run build + build:public clean Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
73 lines
3.3 KiB
JavaScript
73 lines
3.3 KiB
JavaScript
'use strict';
|
|
|
|
/**
|
|
* 工单人机验证契约：ticket_create / ticket_reply 两个场景必须在三处对齐
|
|
* （PHP 场景白名单 / 后台「启用场景」勾选列表的 PHP schema / SPA schema），
|
|
* 且旧的 after_sale_* 场景已彻底移除。
|
|
*/
|
|
|
|
const assert = require('node:assert/strict');
|
|
const fs = require('node:fs');
|
|
const path = require('node:path');
|
|
const test = require('node:test');
|
|
|
|
const root = path.resolve(__dirname, '../..');
|
|
const read = (file) => fs.readFileSync(path.join(root, file), 'utf8');
|
|
|
|
const SCENES = [
|
|
{ key: 'ticket_create', label: '提交工单' },
|
|
{ key: 'ticket_reply', label: '回复工单' },
|
|
];
|
|
|
|
test('ticket captcha scenes are registered in all three places', () => {
|
|
const captcha = read('inc/modules/captcha.php');
|
|
const permissions = read('src/Admin/Schema/SchemaPermissions.php');
|
|
const adminSchema = read('assets/admin/src/schema/sections/permissions/index.js');
|
|
|
|
for (const scene of SCENES) {
|
|
assert.match(captcha, new RegExp(`'${scene.key}'\\s*=> __\\('${scene.label}', 'aksrt'\\)`),
|
|
`captcha scene ${scene.key} missing`);
|
|
assert.ok(permissions.includes(`'label' => '${scene.label}', 'value' => '${scene.key}'`),
|
|
`PHP permissions schema missing ${scene.key}`);
|
|
assert.ok(adminSchema.includes(`{ label: '${scene.label}', value: '${scene.key}' }`),
|
|
`SPA permissions schema missing ${scene.key}`);
|
|
}
|
|
});
|
|
|
|
test('the after-sale captcha scenes are gone', () => {
|
|
for (const file of [
|
|
'inc/modules/captcha.php',
|
|
'src/Admin/Schema/SchemaPermissions.php',
|
|
'assets/admin/src/schema/sections/permissions/index.js',
|
|
]) {
|
|
const src = read(file);
|
|
assert.ok(!src.includes('after_sale_apply'), `${file} still declares after_sale_apply`);
|
|
assert.ok(!src.includes('after_sale_cancel'), `${file} still declares after_sale_cancel`);
|
|
assert.ok(!src.includes('申请售后'), `${file} still carries the 申请售后 label`);
|
|
assert.ok(!src.includes('撤销售后'), `${file} still carries the 撤销售后 label`);
|
|
}
|
|
});
|
|
|
|
test('the ticket REST layer consumes both scenes exactly once', () => {
|
|
const rest = read('src/Ticket/TicketRest.php');
|
|
assert.match(rest, /const CAPTCHA_SCENE_CREATE = 'ticket_create';/);
|
|
assert.match(rest, /const CAPTCHA_SCENE_REPLY = 'ticket_reply';/);
|
|
assert.equal((rest.match(/require_captcha\(\$request, self::CAPTCHA_SCENE_/g) || []).length, 2,
|
|
'create and reply must each verify captcha exactly once');
|
|
assert.equal((rest.match(/aksrt_require_captcha\(/g) || []).length, 1,
|
|
'captcha verification must funnel through one helper');
|
|
});
|
|
|
|
test('the ticket panel mounts both captcha scenes', () => {
|
|
const renderer = read('inc/helpers/user-center-renderers/profile-tickets.php');
|
|
assert.ok(renderer.includes("aksrt_render_captcha('ticket_create')"), 'create mount missing');
|
|
assert.ok(renderer.includes("aksrt_render_captcha('ticket_reply')"), 'reply mount missing');
|
|
assert.ok(!renderer.includes('after_sale'), 'renderer must not mount after-sale scenes');
|
|
|
|
const js = read('assets/js/ticket-center.js');
|
|
assert.match(js, /runCaptcha\('ticket_create'\)/);
|
|
assert.match(js, /runCaptcha\('ticket_reply'\)/);
|
|
// 取消验证时中止提交，不静默放行。
|
|
assert.match(js, /return payload === null \? Promise\.reject\(\{ cancelled: true \}\)/);
|
|
});
|