Linux support #59
Merged
Linux support #59
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
Looks like I missed a file
Codecov Report
@@ Coverage Diff @@
## main #59 +/- ##
==========================================
+ Coverage 77.95% 77.97% +0.02%
==========================================
Files 51 51
Lines 4577 4577
==========================================
+ Hits 3568 3569 +1
+ Misses 1009 1008 -1
Continue to review full report at Codecov.
|
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.
Builds on Linux!
The testsuite has revealed the following limitations on Linux:
ParseFilecurrently doesn't work. This is because the SDK is currently setup for iOS, macOS, etc. There's probably a simple way to access the file system on Linux via Swift that can be added at some point.ParseLiveQuerycurrently doesn't work in the latest version of Swift (5.3.2).FoundationNetworkingdoesn't haveURLWebSocketSessionTask. The solution is to wait to for web socket support to be added in a newer version of Swift.Keychaincurrently doesn't work in the latest version of Swift (5.3.2). The workaround for this has already been added in the SDK. Devs need to conform toParseKeyValueStoreif they want to persist the current user, installation, and config. Otherwise they only exist in memory while the SDK is running.ParseEncoder.