Salesforce metadata: better errors if config is invalid
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 24
- Forks
- 41
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 12
Description
In salesforce - and indeed other adaptors - the metadata function should throw better errors if there are problems in config.
For example, what if credentials are wrong? What if loginurl is not defined?
A general validation preflght check would be a good way to throw nice, human readable errors
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the Salesforce adaptor's metadata function and inspect how invalid credentials and a missing loginurl currently surface. Compare the metadata functions in other adaptors to determine the scope of a general preflight check; done means invalid configuration produces clear, human-readable errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100