Swiftpm support - Githubissues

Tyler-Keith-Thompson commented 3 years ago

Checklist:

[x] Is the linter reporting 0 errors?
[ ] Did you comply with our styleguide?
[ ] Is there adequate test coverage for your new code?
[ ] Does the CI pipeline pass?
[ ] Is the static analysis tool reporting 0 issues?
[x] Did you update the documentation?
[ ] Did you update the sample app?
[ ] Do we need to increment the minor/major version?
[ ] Did you change the public API?
[ ] Have you done everything you can to make sure that errors that can occur are compile-time errors, and if they have to be runtime do you have adequate tests and documentation around those runtime errors? For more details.

[ ] Did you deprecate (rather than remove) any old methods/variables/etc? Our philosophy for deprecation.
[ ] Have you done the best that you can to make sure that the compiler guides people to changing to the new API? (Example: the renamed attribute)
[ ] If necessary, have you tested the upgrade path for at least N-1 versions? For example, if data persists between v1 and v2 then that upgrade should be tested and as easy as we can make it.

Tyler-Keith-Thompson commented 3 years ago

Heya folks. Thought I'd save somebody a little trouble and move the swiftpm stuff up a directory so people can actually use swiftPM.

Tyler-Keith-Thompson commented 3 years ago

Something is wrong with our xcode coverage shell script but I haven't the faintest idea what, it is likely unrelated to the PR.