Bugfix Parsequery Parsefile ParseGeopoint ParseEncoder #131
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
Many bugfix after Bugix after release v.1.016
Function toPointer() in ParseObject
RodrigoSMarques
changed the title
|
Hey Rodrigo Thank you for this, but again, please can you create a merge request with the latest branch (1.0.16). Half of this work has been done and will cause merge conflicts again. Thanks in advance. |
|
Actually, don't worry. I can make the changes. I think there is only 2 small changes here that change the current logic. I will add them later on. |
|
Close. |
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.
Bugfix Parsequery Parsefile ParseGeopoint ParseEncoder, after release v1.0.16.
All changes have been tested.
This PR is aligned with my PR prior to the creation of version v1.0.16