jsforce / jsforce/jsforce-metadata-tools
Give an option to deploy using the tooling api
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
The tooling api is generally faster so it would be nice if there was an option to deploy using that instead of the metadata api
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
Review how deployments currently use the Metadata API, then investigate the Tooling API's deployment capabilities and how an option could fit the existing tool. Done means users can choose the Tooling API for deployment while the current Metadata API path remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100