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

updates forceng to recent version of force.js from salesforce #10

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jaygauten
Copy link

feature: forceng.js update
impact: salesforce api/request calls
scope: native mobile (iOS, Android)
changes:
- refactor logic on loginWithPlugin
- refactor error response from plugin to fix blank error message on failed request
- changed method in update method from post to patch
- other salesforce changes in force.js

@@ -37,7 +37,7 @@ angular.module('forceng', [])

// Only required when using REST APIs in an app hosted on your own server to avoid cross domain policy issues
// To override default, pass proxyURL in init(props)
proxyURL,
proxyURL = baseURL,
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why are we defaulting the proxyURL to baseURL?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

finally see your comment. 💃

@mattgoldspink
Copy link

@frankvlocity @jegauten The changes here seem to force the file to only assume it will be used on mobile. Can we do it in a way where we don't force it to only assume it will be used on mobile because for example we'll use this in Omni in omniout?

@jaygauten
Copy link
Author

@frankvlocity @jegauten The changes here seem to force the file to only assume it will be used on mobile. Can we do it in a way where we don't force it to only assume it will be used on mobile because for example we'll use this in Omni in omniout?

hi @mattgoldspink im not sure which part are you referring to but as far as i know most of the changes can support both mobile and web, though there is one change that allow api calls via plugin but only if the networkPlugin is present otherwise it will use the browser

function getURLs() {
return {proxyURL:proxyURL,oauthCallbackURL:oauthCallbackURL, useProxy: useProxy};
}

function isOnMobile() {
return true;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jegauten RE: it being mobile only.

This line is what seemed to suggest it's going to be focussed on purely mobile. You're always returning true. Is this right?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a good catch. I don't think we use that. Let me check with team.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks Matt.

yes we dont use that we have a flag on our own in the app.js

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we safely remove it so it's clear it's not needed/used?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes it will be removed

@frankvlocity
Copy link

Who has the permission to pull in the change and close this? @mattgoldspink @haxaco ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants