Fix language selector #641
Merged
Conversation
This file contains hidden or 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
davimacedo
requested changes
Jul 14, 2019
Member
davimacedo
left a comment
davimacedo
left a comment
There was a problem hiding this comment.
Can you please pin 3.4.1 instead? I've just tested here and it seems that they have fixed the bug in the newest version.
Contributor
Author
|
@davimacedo even better! Done, I tested it as well and it seems good! |
Contributor
Author
|
I want to get this in so I’ve gone ahead and merged, should be fine 😉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As identified here - https://community.parseplatform.org/t/parse-ios-sdk-guide-language-selection-broken/556
The culprit was a jquery update.
Fixes #643