Remove reliance on JSForce #742
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
☁️ Nx Cloud ReportCI is running/has finished running commands for commit ed9b8a8. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
Added ApiConnector library and added Salesforce API's with 100% coverage from what is used in Jetstream's API Removed all browser dependency on @jetstream/api-interfaces in preparation for deprecation
Refactored all API controllers to use new ApiConnection service Implemented OAuth integration to Salesforce
paustint
force-pushed
the
poc/generic-salesforce-api
branch
from
45654a9 to
96dfc5c
Compare
…sforce There are still a few stragglers with electron and some service services (only used by electron), but everything else is 100% moved away from relying on jsforce types
Removed basePath from ApiConnection added helpers for constructing REST and BULK api paths
Improved loading label for creating object Improved log message for error http response
Worked around layout issue for activities in related list Added profile/perm set name to output file
Move record operation request to stand-alone controller Convert anonymous results back to valid XML Improve download for automation control to also include the actual flow normalize error message for all record operations in cases where SFDC returns a completely different error shape (e.x. invalid URL) Fix progress ring to avoid janky head placement fix API types for deployment - testLevel was missing and was ignored Fixed SOAP requests when the field is null/undefined to avoid it from being included in SOAP request body Ensure responseType parameter is used for manual requests (e.x. get record body) Fix clone record, invalid related data was being included in record which caused issues saving Upgrade slds ot latest version
|
@SocketSecurity ignore-all |
Axios upgrade caused issue with Electron axios Adapter (Which wasn't even actually used)
Added loglevel to environment variable fixed session refresh for SOAP api requests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JSForce does not work well in the browser and limits possibility for using api services anywhere but the server.
fetchimplementation so that this this runs agnostic to a specific environment