Removes the cache options to resolve expected behaviour

[shaps80]

AFAICT the cache policy is kind of a requirement or feature or the Combine approach. Whereas for an async call, this is not actually relevant or likely expected behaviour.

As such, I force it to not use any local caching.

Thanks for raising 👍

Additionally, this PR removes Yarn dependency in favour of PNPM and deletes the dead code files that we aren't and won't be using in the future.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
swift-graphql	❌ Failed (Inspect)			Jan 14, 2024 1:44pm

[maticzav]

@shaps80 could you elaborate what this does in more detail? Why is it necessary? Only writing a PR title is not enough.

[shaps80]

@maticzav apologies you're right. I'll update the description but essentially AFAICT the cache policy is kind of a requirement or feature or the Combine approach. Whereas for an async call, this is not actually relevant or likely expected behaviour.

As such, I force it to not use any local caching.

Thanks for raising 👍

[yonaskolb]

@shaps80 could you elaborate what this does in more detail? Why is it necessary? Only writing a PR title is not enough.

@maticzav there's a bit more context here #184 (comment)

[shaps80]

@shaps80 could you elaborate what this does in more detail? Why is it necessary? Only writing a PR title is not enough.

@maticzav there's a bit more context here #184 (comment)

👍 thanks for this!