-
Notifications
You must be signed in to change notification settings - Fork 33
Company Management Documentation #654
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: releases/b2b-nov-release
Are you sure you want to change the base?
Conversation
This PR adds the company-management dropin documentation (17 files). Enrichment files are already in the base branch (releases/b2b-nov-release). Base: releases/b2b-nov-release
e3d4490 to
d090029
Compare
d090029 to
59b9cd5
Compare
- Convert all parameter descriptions to verb-first, action-oriented form - Provide useful context beyond parameter names - Ensure consistency across all Company Management containers
…tation parameters
slavvka
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the documentation work! I've added missing JSDoc to the dropin code so auto-generation will be more accurate.
PRs with JSDoc additions:
Dropin code: https://github.com/adobe-commerce/storefront-company-management/pull/67
Added JSDoc to 17 files (API functions, types, container props)
Boilerplate docs: https://github.com/adobe-commerce/aem-boilerplate-commerce/pull/996
Fixed incorrect prop docs in 2 block READMEs
Once these are merged, pull the latest dropin code and regenerate. The rest of my feedback is in separate comments above.
| "CompanyProfile": { | ||
| "description": "Manages company profile information including legal name, VAT/Tax ID, contact details, and payment/shipping configurations.", | ||
| "parameters": { | ||
| "withHeader": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CompanyProfile container only supports the className parameter.
Remove these parameters:
- withHeader
- withWrapper
- approvalRuleID
- routeApprovalRulesList
- routePurchaseOrderDetails
- onBack
- onSuccess
- onError
- purchaseOrderId
- requisitionListId
- routeRequisitionList
- routeRequisitionListView
- companyId
- userId
The container implementation (CompanyProfile.tsx line 26-29) only extends HTMLAttributes, which means it only accepts standard HTML div props including className.
| import { initializers } from '@dropins/tools/initializer.js'; | ||
| import { initialize } from '@dropins/storefront-company-management'; | ||
|
|
||
| const customStrings = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be:
const customStrings = {
'Company.shared.fields.companyName': 'Organization Name',
'Company.shared.buttons.save': 'Save Changes',
'Company.CompanyProfile.containerTitle': 'Company Profile',
};
|
We merged our PRs |
Restore enrichment and checkout files to match the base branch state. These files should remain unchanged in this PR as they are not part of the Company Management documentation.
ac84963 to
4d3584b
Compare
… examples - Update customStrings example to use actual dictionary keys: Company.shared.fields.companyName Company.shared.buttons.save Company.CompanyProfile.containerTitle - Replace generic placeholder keys with verified keys from dictionary
- Bump version from beta24 to beta27 - Update CSS classes for new UI components - Update dictionary keys and function descriptions - Preserve correct dictionary examples in initialization - Fix Company Switcher enrichment parameters
…gement-v2 # Conflicts: # _dropin-enrichments/company-management/containers.json # _dropin-enrichments/company-switcher/containers.json
Feature branches now receive safeguard files (Git hooks, GitHub Actions, publication docs) when merged from releases/b2b-nov-release. The validation script needs to explicitly allow these files: - .githooks/ directory - .github/workflows/ (safeguard workflows) - All .md files (includes PUBLISH-B2B-README.md, etc.) This prevents false validation failures on feature branches.
Changed pattern from ^\.github/workflows/ to ^\.github/ to include files like .github/PULL_REQUEST_TEMPLATE_PUBLICATION.md This was causing validation failures because the PR template is in .github/ root, not in workflows/ subdirectory.
The validation workflow is blocking all PRs. Disabling it temporarily to unblock the team while we diagnose the root cause. The workflow file is renamed to .yml.disabled so it won't run.
Change broken links from /merchants/blocks/targeted-block/ to /merchants/commerce-blocks/personalization/ to fix build errors.
Applied same fixes as b2b-preview (commit e70bec4): - Complete B2B dropins sidebar with all 4 dropins - Restored 30 B2B commerce block files - Added B2B Commerce blocks section to sidebar
| - name: Install dependencies | ||
| if: success() || failure() | ||
| run: npm ci || npm install | ||
| run: npm ci --legacy-peer-deps || npm install --legacy-peer-deps |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What was the motivation for this change? It seems to introduce the risks of increased technical debt over time. Also, there is mixing between pnpm and npm. Is it necessary to use both?
Note: This PR supersedes #619 with a cleaner file structure for easier review.
Company Management Documentation
Complete documentation for the Company Management B2B drop-in.
📖 Preview
Full preview with all dropins: https://commerce-docs.github.io/microsite-commerce-storefront/dropins-b2b/company-management/
📁 Files Added
✅ Review Checklist
Part of #600 - B2B Documentation Initiative