First, I want to say thank you for reading this -- as this project is a bit of an experiment. We really need community contributors and volunteer developers for b2c-crm-sync to live up to its promise as a trustworthy integration foundation for B2C Commerce and the Salesforce Platform.
The Salesforce Community, Salesforce Architects, Salesforce Partners, and the SCPPE and Service Delivery teams within the Customer Success Group (CSG) all contribute to this repository. This repository isn’t supported by Salesforce Commerce Cloud or Salesforce Platform Technical Support. For feature requests or bugs, please open a GitHub issue. Contributions are ALWAYS WELCOME -- and you can feel great about contributing back.
All our mocha-tests live in the test folder off the folder root. Here, you'll find unit tests for our CLI tools, our B2C cartridges, and multi-cloud unit tests that exercise both integration environments via REST APIs. We also have Apex unit-tests you can use to exercise our Apex code.
Tests create trustworthiness, and trustworthiness is important to us. If you're looking for a way to contribute, growing our test-coverage is a really great way to give back. We are ALWAYS looking to improve our test coverage.
Please send a GitHub Pull Request to b2c-crm-sync with a clear list of what you've done (read more about pull requests). When you send a pull request, we will extol your praises if you include comments and pull-requests. We can always use more test coverage. Please make sure all of your commits are atomic (one feature per commit).
Always write a clear log message for your commits. One-line messages starting with the issue number are fine for small changes. Bigger changes should look like this:
$ git commit -m "#1 A brief summary of the commit
>
> A paragraph describing what changed and its impact."Issue numbers at the front of commit messages make it easier for us to follow changes as they're coming in. Your willingness to align to this standard is appreciated.
Start reading our code, and you'll get the hang of it. We optimize for readability:
- We indent using four spaces (soft tabs)
- We have an "interesting" mix of ES6 and ES5 code (don't hate the var statements in our B2C Commerce cartridges)
- The project includes an ESLint configuration file; please use it.
Remember that this is an enablement solution that teaches how to integrate B2C Commerce with the Salesforce Platform. It's community contributed and driven. That said, consider the people who will read your code -- and make it look nice for them.
Above all else, let's #wintogether. Nothing would make me happier than to have to ask my Manager for more Hoody Budget because we're getting so much support.
Thanks from all of us! Looking forward to hearing from you. :)
Best 💜 💜 💜
"Sister from Another Mister"
Senior Regional Success Architect
Christa Matukaitis
"Artisan Flow-Master"
Regional Success Architect
Eric Schultz
"Has Re-Written More of My Code than I Have"
Senior B2C Technical Architect
Jordane Bachelet
"Tenacious, Relentless, and Continuous"
Regional Success Architect
Olena Baykur
"Yes, These Are My Nicknames For Everyone"
Lead Evangelist: B2C Solution Architect Program
Abraham Lloyd