SwiftUI Example Project

[amyoulton]

This is an ongoing draft PR for collaboration/feedback as we continue to build out the project

The new example project is being built out with SwiftUI. I have set the project settings and built out a mock "API" using Swifter.

I originally wanted to included live previews within the application, but because the network is being run within the application, if you have a build open, the live preview throws a fatal error because a port is already open. That's the nature of the network being within the app. Since it's a super fast app to build, so I've chosen to keep live previews off.

The Project

Currently, I've added the following things into the new SwiftUI project:

The "API"

This includes my JSON data that I will continue to add to, and my network that leverages Swifter. I have currently added JSON data for:

• posts
• version

I'll update the above list as the project continues getting built out, as more JSON will be added.

The Build

• HomeView & HomeVM (containing posts and a version print)
• Post Repo & Version Repo, to showcase different Netable Requests. Version serves to be the most "basic" form of a request from start to finish, so despite it being small I wanted to keep it seperate. Posts will likely keep expanding with more request options as I continue.
• PostRequest & Version Request. Similar to above, Post will likely keep expanding to showcase using other features.

[brendanlensink]

Another thing I forgot to mention: We should go through the app with concurrency checking set to Complete and try and sort out any warnings it's throwing. Even with minimal it's throwing >10 😬

[amyoulton]

@brendanlensink Woo! Tons of changes & updates made. 🔥

Here are the significant ones I can think of to report on:

• updated login to have its own view/VM, which cleans up a lot
• simplified the get user call
• separated the error view
• added in the .lossy decoding strategy within the post request
• added a LossyArray to the user object
• updated the post json, the user json, and added an extra json file for the graphql request
• change the graphql get request to use smart unwrap instead
• did a solid walk through every file to check for formatting & cleaned up and refactored. I also temp re-added swift lint to double check!
• lots of updates on the README file - links will need to be updated post-merge as they're currently pointing to this branch.

I did some other small tidies but they've escaped me 😅

[amyoulton]

@brendanlensink looking through this PR again after the break apparently let my eyeballs actually work because I seemed to entirely ignore that concurrency checking comment.

I have some questions I've left on your above comments!

So I will need to do that as well and then re-submit, which will I believe will warrant a re-review. Thoughts?

[amyoulton]

@brendanlensink alright, this should be final review 🥳 I've added the changes, removed the example project and updated the links. I have not added in Sendable conformance though, because this is turning out to be a lot more of a headache than expected.

Since for the most part, conforming to Sendable will happen outside of my project, I was thinking that once this is merged, I'll rebase #115 and conform to Sendable for Netable on that issue, while also adding the few conformances to the example project at the same time, since they will be so interwoven, and the example project does a great job of really showing where the conformance issues lie!

Let me know your thoughts on this, but either way I believe we should merge this first!