Fix package dependency syntax

[alexandrethsilva]

@designatednerd I went ahead and made the PR related to #1102 in case you'd like to have it merged as I will probably be offline for a few hours.

One thing I'd like to ask though, is whether it would make sense to have the officially suggested syntax pointing to an exact version rather then a range and updating the docs as new versions are released, as in:

.package(name: "Apollo", url: "https://github.com/apollographql/apollo-ios.git", .exact("0.24.0"))

I ask for a few reasons:

• You point out right below that the version should be an exact match to the one in the main project, but the unaware user may end up mixing things? That would also make it more in line with the iOS SDK setup docs which favour the version to be up to the next minor only?
• It makes it easier to debug opened issues, since you'd know the exact version installed instead of having to guess or depend on the reporter double-checking it?
• It avoids propagating new bugs to people that setup their projects earlier and end up pulling a later version in the range (even if minor) which contains a bug?

Let me know if any of this makes sense and whether I should update the PR to make it align with these points.

Cheers!

[apollo-cla]

@alexandrethsilva: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/

[designatednerd]

I think this issue points to me needing to update something in Package.swift- you absolutely shouldn't need to do this manually.

Good call on the from though - I should probably update that to get up to the next minor to match our recommendation for the main repo

[alexandrethsilva]

@designatednerd should I drop this PR for the time being or would you like me to maybe take a different approach?

[designatednerd]

Let's leave this up for now, I'm working on a fix but until it's actually ready this will at least help anyone who's stuck

[designatednerd]

@alexandrethsilva I'd like to close this out in favor of #1106 - I really appreciate you taking the time to make this but I want to have the extra context I've added in that PR. is that cool?

[designatednerd]

Went ahead and merged #1106 so I'm gonna close this out - thanks again for helping figure this out!

[alexandrethsilva]

Hi @designatednerd, sure! Glad that I could help out a bit. 🤓