Skip to content
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

Switch to JSForce 2.0 #196

Closed
4 tasks done
acrosman opened this issue Apr 14, 2023 · 1 comment · Fixed by #206
Closed
4 tasks done

Switch to JSForce 2.0 #196

acrosman opened this issue Apr 14, 2023 · 1 comment · Fixed by #206
Labels
dependencies Pull requests that update a dependency file enhancement New feature or request

Comments

@acrosman
Copy link
Owner

acrosman commented Apr 14, 2023

Summary
Switch to JSForce 2.0 and perform any needed updates.

Please describe the problem you are trying to solve.
Staying current for security releases and other enhancements.

Proposed Solution
All current development effort of JSForce, the library used for all calls to Salesforce, is on the 2.0 branch. It's good enough for SFDX it should be good enough for this project. Not sure all the changes needed between 1.x and 2.0, but it's probably time.

Calls needing promise conversion

  • sf_describeGlobal
  • sf_getObjectFields
  • sf_login
  • sf_logout
@acrosman acrosman added enhancement New feature or request dependencies Pull requests that update a dependency file labels Apr 14, 2023
@acrosman acrosman mentioned this issue May 3, 2023
@acrosman
Copy link
Owner Author

Appears this requires updating all callbacks to promises. A good call overall, but a bit of work across the code base.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant