-
Notifications
You must be signed in to change notification settings - Fork 8
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
salesforce: docs deep dive #664
Comments
I won't be able to work on this issue this week, We should probably promote to next week sprint |
@aleksa-krolls this issue |
@josephjclark i need second opinion, is this a good first issue for salesforce adaptor ?. I am curios if we should start with #663 ? |
@mtuchi We need a good round of documentation and unit tests before we port the jsforce version. The idea is to have a stable base to migrate from. It may help catch issues in the library. So an ideal start is to go through and make sure docs are a) complete and b) accurate. That doesn't mean hundreds of words - it means links to salesforce or jsforce documentation, it means state tables and maybe object definitions, it means concise and helpful examples. |
EOD Update #799 |
Hey @mtuchi what is status here? Pls leave EOD updates... especially on Friday! Also, if there is work left here - pls make sure to prioritize client work before picking this back up. |
I have a draft PR already i just need to clean up and ask Joe for review, I will pick this up tomorrow |
EOD Update This is done and ready for review, See #821 |
This issue is to do a deep docs review on Salesforce. I expect to contribute heavily to this myself.
good examples
Requirements:
The text was updated successfully, but these errors were encountered: