| .. |
|
apply.vue
|
2886587a15
feat: replace user-facing '孩子' terminology with '成员'/'家庭成员' across frontend - assessment flow, family member pages, health questionnaires, activity pages, and UI text updates per product decision that system has no 'child' concept; users see only self + family members, child status derived from relationship; internal entity/DB references (Child entity, child_id columns) preserved unchanged
|
1 день назад |
|
execution.vue
|
508427acae
fix: 小程序前端 GET 请求全部改为 POST + 成长打卡页美化与自动返回
|
1 месяц назад |
|
purchase.vue
|
2886587a15
feat: replace user-facing '孩子' terminology with '成员'/'家庭成员' across frontend - assessment flow, family member pages, health questionnaires, activity pages, and UI text updates per product decision that system has no 'child' concept; users see only self + family members, child status derived from relationship; internal entity/DB references (Child entity, child_id columns) preserved unchanged
|
1 день назад |
|
quota.vue
|
32086f9276
fix: 测评/心智页面日期解析改用 parseDate（iOS 兼容）
|
2 месяцев назад |
|
rating.vue
|
508427acae
fix: 小程序前端 GET 请求全部改为 POST + 成长打卡页美化与自动返回
|
1 месяц назад |
|
results.vue
|
2886587a15
feat: replace user-facing '孩子' terminology with '成员'/'家庭成员' across frontend - assessment flow, family member pages, health questionnaires, activity pages, and UI text updates per product decision that system has no 'child' concept; users see only self + family members, child status derived from relationship; internal entity/DB references (Child entity, child_id columns) preserved unchanged
|
1 день назад |
|
upload-report.vue
|
2886587a15
feat: replace user-facing '孩子' terminology with '成员'/'家庭成员' across frontend - assessment flow, family member pages, health questionnaires, activity pages, and UI text updates per product decision that system has no 'child' concept; users see only self + family members, child status derived from relationship; internal entity/DB references (Child entity, child_id columns) preserved unchanged
|
1 день назад |
Sisyphus
2886587a15
feat: replace user-facing '孩子' terminology with '成员'/'家庭成员' across frontend - assessment flow, family member pages, health questionnaires, activity pages, and UI text updates per product decision that system has no 'child' concept; users see only self + family members, child status derived from relationship; internal entity/DB references (Child entity, child_id columns) preserved unchanged