jsforce / jsforce/jsforce-metadata-tools
Behind http Proxy need new connection property to pass to jsforce
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
JSForce has http Proxy so can we have that in connection option in here? since we are unable to get through that proxy
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
Start by tracing how connection options are passed to JSForce in this metadata-tools repository and compare that with JSForce's HTTP proxy support. Done means users can provide a proxy through the connection options and use the Metadata API through that proxy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100