1.8 KiB
1.8 KiB
frontend -> frontendNew migration status
Completed scope
frontendNewis the only supported application surface. Character routes are under/dcalc/character/:alter/(equipment|skill|forge|result); legacyfrontendURLs are not redirected or maintained.- The existing API contracts, Pinia configuration schema, and
dcalc/<alter>/configstorage keys remain unchanged. - Equipment, Skill, Forge, imports, result details, baseline comparison, and change-source logs
are implemented in
frontendNew.
Parity safeguards added
- Suite double-click now applies the selected rarity as an idempotent bulk wear operation for both equipment and oaths. It never toggles already equipped items off.
- Equipment choices and bulk wear actions append a single
Equipmentchange-source record; Skill, Forge, and import actions keep their existing records. - Character configuration changes are debounced and serialized. A change received during an active calculation queues one follow-up calculation and every completed attempt persists the latest configuration.
- Character switches reset in-memory configuration and skill counts before loading that role's
persisted data. Stale character responses are ignored by their
Alter-Token. - The unused global result sheet was removed from the Character shell. Equipment, Skill, and Forge
retain their one local summary panel;
/resultremains the full calculation-detail route.
Out of scope
- Legacy
frontendbuild errors and its uncommitted files are not modified. - DNF VP remains a
frontendNew-only feature. - No backend API, request payload, configuration field, or local-storage migration is introduced.
See MIGRATION_FUNCTION_MATRIX.md and MIGRATION_REGRESSION_CHECKLIST.md for acceptance coverage.