forked from parse-community/Parse-SDK-Android
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Up merge with base repository #2
Open
johncordeiro
wants to merge
126
commits into
Ilhasoft:master
Choose a base branch
from
parse-community:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
The service definition "com.parse.fcm.ParseFirebaseMessagingService" was missing the ">" character at the end, causing error in AndroidManifest.xmll
* Implement generic delegate for attributes Signed-off-by: Daniel San <[email protected]> * Implement specialized property delegation for boolean Signed-off-by: Daniel San <[email protected]> * Implement specialized property delegation for double Signed-off-by: Daniel San <[email protected]> * Implement specialized property delegation for float Signed-off-by: Daniel San <[email protected]> * Implement specialized property delegation for int Signed-off-by: Daniel San <[email protected]> * Implement specialized property delegation for long Signed-off-by: Daniel San <[email protected]> * Implement specialized property delegation for string Signed-off-by: Daniel San <[email protected]> * Implement specialized property delegation for bytes Signed-off-by: Daniel San <[email protected]> * Implement specialized property delegation for map Signed-off-by: Daniel San <[email protected]> * Implement specialized property delegation for list Signed-off-by: Daniel San <[email protected]> * Implement specialized property delegation for JsonArray Signed-off-by: Daniel San <[email protected]> * Implement specialized property delegation for JsonObject Signed-off-by: Daniel San <[email protected]> * Implement specialized property delegation for ParseRelation Signed-off-by: Daniel San <[email protected]> * Implement specialized property delegation for Enum Signed-off-by: Daniel San <[email protected]> * Implement generic delegate for attributes with some checks Signed-off-by: Daniel San <[email protected]> * Small fix on ParseDelegate set property type Signed-off-by: Daniel San <[email protected]> * Add basic documentation to all delegate classes Signed-off-by: Daniel San <[email protected]> * Add property delegation documentation on README.md Signed-off-by: Daniel San <[email protected]> * Update kotlin version Signed-off-by: Daniel San <[email protected]>
* Add test for StackOverflowError during mergeFromServer This test shows the #896 bug. * Make a synchronized copy of availableKeys `synchronizedSet(s)` ends up making a new wrapper for the supplied set, which means on subsequent calls, it becomes a SynchronizedSet, wrapped in a SynchronizedSet, wrapped ... etc. When using the LocalDataStore, the ParseObject.State is reused for every matching ClassName+ObjectId pair, so every time a ParseObject is parsed from JSON data, the existing object is "refreshed" by making a copy of its State, and then merging with the new data. Every call to State.newBuilder() is therefore adding a new layer of SynchronizedSet to the availableKeys Set. Eventually that nested hierarchy of sets becomes so large that it causes a StackOverflowError for any operation on the collection. By making a copy of the set before wrapping it in synchronizedSet(), that nested hierarchy becomes severed, and we end up with just one level of wrappers. * Accept the updated Android Build-Tools 27 license
* Implement extensions to ParseQuery to use property's name as key instead of strings Signed-off-by: Daniel San <[email protected]> * Update README to show ParseQuery extensions Signed-off-by: Daniel San <[email protected]>
* Expose useful constants Signed-off-by: Daniel San <[email protected]> * Fix import order Signed-off-by: Daniel San <[email protected]>
* Create CODE_OF_CONDUCT.md * change email
…ault Parse Query limit of 100 objects. (#939)
* Fix for #499 Signed-off-by: Daniel San <[email protected]> * Avoid code smell According to SonarLint this is a necessary change to avoid code smell: https://rules.sonarsource.com/java/tag/brain-overload/RSPEC-135 Signed-off-by: Daniel San <[email protected]>
* Add Coroutines suport Call parse query find as a suspend function Call login and singup as a suspend function Call cloud function as a suspend function * Add coroutines README link at root project
* Add more operation extensions to parse query * Add a coroutine builder to call parse query operations as a receiver * Change package structure * Add parse object support
* expose client destroy * fixed duplicate method
* update code docs for destroy * added setServer and getServer
* added warning to update server URL docs * fixed typo
* Google log in * Adjustments for Java caller * Fix docs * Add more auth data and sign out once complete
* Updates to dependencies and README * Add more notice to GCM module
BREAKING CHANGE: The required minimum API level changes from 16 to 21. The following deprecated methods are removed: `Parse.getParseDir()` (use `getParseCacheDir(String)` or `getParseFilesDir(String)` instead), `ParseTwitterUtils.link(ParseUser, Context)` (use `linkInBackground(Context, ParseUser)` instead), `ParseTwitterUtils.link(ParseUser, String, String, String, String)` (use `linkInBackground(ParseUser, String, String, String, String)` instead).
# [3.0.0](2.1.0...3.0.0) (2021-11-25) ### Features * update project dependencies and code refactoring ([#1147](#1147)) ([7d0faa3](7d0faa3)) ### BREAKING CHANGES * The required minimum API level changes from 16 to 21. The following deprecated methods are removed: `Parse.getParseDir()` (use `getParseCacheDir(String)` or `getParseFilesDir(String)` instead), `ParseTwitterUtils.link(ParseUser, Context)` (use `linkInBackground(Context, ParseUser)` instead), `ParseTwitterUtils.link(ParseUser, String, String, String, String)` (use `linkInBackground(ParseUser, String, String, String, String)` instead). ([7d0faa3](7d0faa3))
…this fixes the bug that was introduced with release 3.0.0 which ignores SDK-internal data that is stored locally on the client side (#1168)
## [3.0.1](3.0.0...3.0.1) (2022-05-26) ### Bug Fixes * users logged out after SDK upgrade due to different cache path; this fixes the bug that was introduced with release 3.0.0 which ignores SDK-internal data that is stored locally on the client side ([#1168](#1168)) ([ec7bd03](ec7bd03))
BREAKING CHANGE: The Facebook Login SDK is upgraded to 13.x; this is a transitive dependency, so if you are directly calling the Facebook Login SDK in your app then this may be a braking change; this release of the Parse Android SDK adds a version range to the Facebook Login SDK dependency for correct gradle dependency resolving
# [4.0.0](3.0.1...4.0.0) (2022-06-10) ### Features * update various dependencies ([#1172](#1172)) ([779dc0b](779dc0b)) ### BREAKING CHANGES * The Facebook Login SDK is upgraded to 13.x; this is a transitive dependency, so if you are directly calling the Facebook Login SDK in your app then this may be a braking change; this release of the Parse Android SDK adds a version range to the Facebook Login SDK dependency for correct gradle dependency resolving ([779dc0b](779dc0b))
# [4.2.0](4.1.0...4.2.0) (2023-02-22) ### Features * Add support for Facebook SDK 15.x ([#1188](#1188)) ([5ebd443](5ebd443))
## [4.2.1](4.2.0...4.2.1) (2023-08-25) ### Bug Fixes * Missing Proguard rules for R8 in full mode ([#1196](#1196)) ([7db0965](7db0965))
# [4.3.0](4.2.1...4.3.0) (2024-02-18) ### Features * Add support for uploading a `ParseFile` from a URI ([#1207](#1207)) ([83aec68](83aec68))
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.
No description provided.