Socializer & MessageFactory improvements #5
Closed
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.
This fixes a few issues with the gigya communication and adds the
socialize.deleteUser
API call. See full commit messages for more info.As for returning the response in
Socializer#notifyLogin()
, we need that since it is required to set the cookie which is provided by the response.We also have a method called
setCookieFromResponse(\SimpleXMLElement $response)
which takes this response and creates a cookie. I can send a PR if you think it should be part of this bundle (and whether it should go intoSocializer
, or maybeHelper/SocializerHelper
).