Explorer/Planner default values (#2347)¶
Problem¶
gh issue view 2347 resolves to a pull request, not a standalone issue —
2347 is the PR number, on branch fix/2061. It delivers part of umbrella¶
issue #2061, "Dynamic default values different in Explorer, Project Planner and Calculator" (#2061 stays open: other sub-items are tracked separately, delivered via other PRs — #1998, #1995, #2000, #2119, #2297).
This PR's slice: in the Explorer's External Cloud & AI form, FTE count
defaulted to 0 instead of empty; in the Explorer's Professional Travel
form, no sensible traveler was pre-selected; in the Explorer's Equipment
form, Equipment ID defaulted to blank instead of "Unknown".
What shipped¶
PR #2347, "fix: apply various default values in planner/explorer forms",
merged 2026-08-25 (32fe8c442). All frontend, 5 files:
frontend/src/constant/moduleConfig.ts— widensModuleField.explorerDefaultfromnumbertostring | number | nullto allow non-numeric sentinel defaults.frontend/src/constant/module-config/equipment.ts— Equipment ID getsexplorerDefault: 'Unknown'.frontend/src/constant/module-config/professional-travel.ts— the traveler field getsexplorerDefault: TRAVELER_OTHER_INTERNAL(Explorer has no headcount roster to pick a real traveler from).frontend/src/constant/module-config/external-cloud-and-ai.ts— removes the oldexplorerDefault: 0for FTE count so it starts empty in Explorer; the Calculator path is unaffected (defaultFrom: 'total_fte'stays).frontend/src/components/organisms/module/SubModuleSection.vue:195— thetotal_ftedefault-fill condition becomesfield.defaultFrom === 'total_fte' && validatedTotals.total_fte, so a validated total of exactly0is treated as "nothing to pre-fill" rather than shown as a misleading0.
No test files were touched in this diff. Note:
frontend/tests/unit/external-ai-fte-explorer-default.spec.ts (from the
earlier #2000/#2061 commit that first set explorerDefault: 0) exercises
the generic resolveExplorerFormDefaults resolver via a synthetic field
object, not external-cloud-and-ai.ts's real config — so it still passes
after this PR removed the real field's explorerDefault, but its docblock
description is now stale.