Fixed buid errors - #52 #53
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
|
Hi @GRSouza. I understand, but your PR goes way beyond the scope of the fix and will probably take more time to review. In the meantime, people like myself can't reset package caches or run any SPM updates without running into this issue. This simply let's people move forward with their work while you wrap up your RC branch and allow it to be properly reviewed and merged |
grdsdev
approved these changes
Jan 4, 2023
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.
What kind of change does this PR introduce?
Fixes build errors mentioned in issue #52 by:
SupabaseClient.swiftWhat is the current behavior?
Fails to build due to breaking changes in
postgrest-swiftWhat is the new behavior?
Now builds and runs as expected
Additional context
Glad to help!