Skip to content

feat(b2b):B2B-4545 Update v2/frontend/companies to include mandatory customerEmail field#1291

Open
bc-akshatkaushik wants to merge 1 commit intomainfrom
B2B-4545
Open

feat(b2b):B2B-4545 Update v2/frontend/companies to include mandatory customerEmail field#1291
bc-akshatkaushik wants to merge 1 commit intomainfrom
B2B-4545

Conversation

@bc-akshatkaushik
Copy link
Copy Markdown
Contributor

@bc-akshatkaushik bc-akshatkaushik commented Mar 26, 2026

B2B-4545

What changed?

  • Update POST v2/frontend/companies request schema to include new required field customerEmail
  • Add validation error example for missing field

Release notes draft

  • Add new required field customerEmail to POST v2/frontend/companies

ping @bc-Vince @bc-sylvialin @chris-nowicki

…ation to include mandatory customerEmail field
@bc-akshatkaushik bc-akshatkaushik marked this pull request as ready for review March 26, 2026 04:21
@bc-akshatkaushik bc-akshatkaushik changed the title feat(b2b):B2B-4545 Update v2/frontend/companies and companyCreate mutation to include mandatory customerEmail field feat(b2b):B2B-4545 Update v2/frontend/companies to include mandatory customerEmail field Mar 26, 2026
Copy link
Copy Markdown
Contributor

@bc-Vince bc-Vince left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes in the Company spec look good. The storefront.yaml file was migrated with other developer docs when we switched from Stoplight, but it does not actually correspond to any live developer documentation. As a result, there is no need to make edits to it.

@bc-akshatkaushik
Copy link
Copy Markdown
Contributor Author

bc-akshatkaushik commented Mar 26, 2026

The changes in the Company spec look good. The storefront.yaml file was migrated with other developer docs when we switched from Stoplight, but it does not actually correspond to any live developer documentation. As a result, there is no need to make edits to it.

Thanks Vince that's good to know, perhaps we can leave the changes in for now, in case they get pulled in by a LLM lookup or the like who doesn't know the difference about what's live and what's not
Until ultimately we can remove the file no longer serving things in Production to avoid the confusion/duplication

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants