For a long time, solving the problem of API integrations between frontend and server-side seemed trivial. You might have stumbled across some HTML form encoding or legacy APIs that relied on SOAP and IML, but most APIs used REST with JSON encoding. While REST looked like the de-facto standard, ironically, it didnāt have a defined [ā¦]
Hey, Iād like to share my experience with going through this tutorial.
You have made an excellent point in declaring the types in the Schema in a specific order. This should also be done in the configure file for the migrations, i.e. we have to declare certain migrations before others as they might depend on each other.
One thing I noticed when trying to flesh out the model is that if we declare a dependency on Graphiti in the models, i.e. if we want to pass in the NoArguments to the request for the child relation, this will lead to segmentation fault. This is easily fixed, just wanted to mention. Iām running Swift 5.5.
It is quite enjoyable tutorial otherwise.
Thank you!
Thanks for the tutorial! However, I am getting stuck right at the beginning.
I opened starter project, waited for the dependencies to download, and then tried to run the app, but got errors like
ā¦TLSConfiguration.swift:24:35: ātls_protocol_version_tā is only available in macOS 10.15 or newer
ā¦TLSConfiguration.swift:27:25: āTLSv10ā is only available in macOS 10.15 or newer
ā¦TLSConfiguration.swift:29:25: āTLSv11ā is only available in macOS 10.15 or newer
Command CompileSwiftSources failed with a nonzero exit code (GraphQL)
Command CompileSwiftSources failed with a nonzero exit code (NIOHTTP2)
I was able to get rid of the errors by updating the various package version numbers. This is the setup which allowed me to compile and run the starter version