SPM compatibility fixes, re-org: WIP #4
Draft
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.
Hi. I have forked your fork and done some re-organization and compatibility expansion. There are a lot of changes in the top-line numbers, but that is mostly due to having duplicated example projects. Mostly this is a deletion / re-organization effort because I like the FW and need SPM support.
This is a draft PR: I am opening this to see if you would like to merge the changes / support the direction I am taking this.
Here is the TL;DR:
Cocoapods, however, still has some import issues, this is a WIP but will address in a subsequent push.
Options for fixing Cocoapods support without maintaining two example projects:
Examples/
folder levelThere is another issue: naming. Idk what the situation is on Cocoapods, but the name collision issues don't necessarily exist when using the framework via SPM because you pull it straight from the repo. As long as you don't use two packages of the same name. Anyway, will propose solution in a future update to the Cocoapods example-- curious to hear any opinions you may have as well of course.