- Ya
- 28 Agosti 2026, 03:49 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 7616db0
withBranchType previously turned useWebAlias on whenever the SELECTED MODEL allowed ROOT or a custom alias, ignoring the three parent-org preconditions BasicsStep.tsx has always required alongside it: subdomain branches enabled, GoDaddy configured, and a root domain to hang the alias off of. Combined with EMPTY_CREATE_ORG_FIELDS defaulting useWebAlias to true, this put every branch type with allowRootSubdomains on the web-alias/ROOT path regardless of whether the parent could actually support it, and toWizardFormData was hardcoding subdomainContext to all-false rather than forwarding what the page was given. Adds **************** and the single webAliasPossible(fields) predicate that reproduces BasicsStep's five-condition check exactly, so later tasks import one definition instead of re-deriving it. withBranchType now gates useWebAlias on webAliasPossible of the prospective (model + context) state and nulls parentAliasId to match, mirroring BasicsStep's own snap-back effect. createOrgReadiness only blocks on a missing parentAliasId when the web-alias path is actually possible, so it can never refuse launch over a field the page had no reason to show. **************** now starts false, matching useWizardForm.ts's own INITIAL_DATA — something turned on once known possible, not defaulted on and snapped back.