Update customer missing fields

[cartamundi-tvae]

Update customer data in Account Settings requires first name, last name and email, and an optional company:

catalyst/core/vibes/soul/sections/account-settings/schema.ts

Lines 11 to 16 in 81b88df

	export const updateAccountSchema = z.object({
	firstName: z.string().min(2).trim(),
	lastName: z.string().min(2).trim(),
	email: z.string().email().trim(),
	company: z.string().trim().optional(),
	});

However, the update function only sends the first name and last name to actually update. The email, nor the company is updated.

catalyst/core/app/[locale]/(default)/account/settings/_actions/update-customer.ts

Lines 19 to 22 in 81b88df

	customer {
	firstName
	lastName
	}

Additionally, if a new field was added later (e.g. Terms and Conditions) which is now required. Then older accounts cannot update their info because the field is required, but there is no option to change it:

1:{"account":"$T0:0:account","lastResult":{"status":"error","intent":"$undefined","initialValue":{"company":"XXXXX","email":"xxxxx@xxx.com","firstName":"XXXX","intent":"update","lastName":"XXXXX"},"error":{"":["Required account form field ID 26 ('Terms and Conditions') is missing"]},"state":"$undefined","fields":["firstName","lastName","email","company","intent"]}}

[chanceaclark]

Thanks for filing this! Dug into it, one part checks out and one part doesn't hold up.

On the email/company piece: doesn't look like a real issue. update-customer.ts already sends both in the mutation input, submission.value includes them since they're part of updateAccountSchema. The lines you linked (19-22) are the mutation's response selection (what gets echoed back), not the input being sent. I confirmed against a test store that both persist fine today.

On the required custom field piece: confirmed, and honestly it's worse than described. BigCommerce revalidates every required custom customer field on every updateCustomer call, not just at registration, and not just for the fields you're actually changing. Tested it directly: a customer with a required field already set (checked a "Terms and Conditions" box in a previous save) still gets

ValidationError: Required account form field ID X is missing

if that field isn't resent on a completely unrelated update, like just changing their first name. Since Account Settings only ever submits firstName/lastName/email/company, any store with a required custom customer field locks customers out of saving anything at all, not just the new field.

For context, this is actually a regression. Custom field support existed in Account Settings before and got dropped during the Vibes redesign; Register and Address kept it.

Opened #3076 to fix it using the same pattern Register and Address already use. Mind giving it a review when y'all get a chance?