976 B
976 B
Implementation Notes
Plan
- Add thin edit-template components that standardize form page coordinates without becoming a JSON form generator.
- Remove
台账工具from reimbursement and asset list pages and migrate its contents into explicit actions, advanced filter areas, row actions or page header actions. - Update frontend design specs so future pages follow the same template and action-placement rules.
- Run frontend typecheck/build and focused text checks for the first batch.
Design Decisions
- The edit template owns layout only: header/action strip, section spacing, validation summary, form grid and sticky bottom action bar.
- Business pages keep their fields, permissions, mutations, state transitions and error handling explicitly in page code.
- The generic
台账工具name is removed from first-batch user-facing pages; every action should use a concrete verb such as导出,统计,批量处理,新建,导入or更多.