add iOS library latest-legacy toggle switch

[phantumcode]

Issue #, if available:

Description of changes:

• Create lib-legacy directory based on the current existing lib directory
• add a v2 (latest) - v1 toggle switch for Amplify iOS V1 and V2

Screenshot:

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[tjleing]

it seems like /lib/[x] files are being replaced with /lib-v1 files -- are redirects in place? on iOS all of the paths should still work (but access a v2 page), but on Android links going to /lib pages will be broken until we add them.

[phantumcode]

it seems like /lib/[x] files are being replaced with /lib-v1 files -- are redirects in place? on iOS all of the paths should still work (but access a v2 page), but on Android links going to /lib pages will be broken until we add them.

Android docs are still available under /lib/ and all links still works. A clone of /lib/ was created and moved to /lib-v1/ for both Android and iOS, links to lib-v1 for Android won't work until they're added. When Android is ready to update to v2, add v2 contents under /lib/ and enable the switcher.

[abdallahshaban557]

@phantumcode - can you please elaborate on why this toggle is needed?

• Are the public APIs exposed to customers significantly different between V1 and v2?
• If I want to migrate between V1 and V2, do I just have to change my project setup?

[phantumcode]

@phantumcode - can you please elaborate on why this toggle is needed?

• Are the public APIs exposed to customers significantly different between V1 and v2?
• If I want to migrate between V1 and V2, do I just have to change my project setup?

Amplify iOS V2 introduces major breaking changes. All public APIs in each categories will be different syntax. It's functionally the same as V1 but introduces Swift's new async/await structured concurrency pattern.

In order to migrate from V1 to V2, customers will need to update the API usages and update the iOS app to adopt the new Swift async/await structured concurrency.

[atierian]

Does it make sense to swap the positions of v1 and v2 (latest)?

┌────────────────┬──────────────────┐
│                │                  │
│      v1        │    v2 (latest)   │
│                │                  │
└────────────────┴──────────────────┘

I see there's precedent for the way you have it here, but it feels wrong to have reverse chronological for LTR languages here.

[lgtm-com]

This pull request introduces 1 alert when merging f9c943a into 2492477 - view on LGTM.com

new alerts:

• 1 for Useless assignment to local variable

[phantumcode]

Does it make sense to swap the positions of v1 and v2 (latest)?

┌────────────────┬──────────────────┐
│                │                  │
│      v1        │    v2 (latest)   │
│                │                  │
└────────────────┴──────────────────┘

I see there's precedent for the way you have it here, but it feels wrong to have reverse chronological for LTR languages here.

Good suggestion @atierian . @hdworld11 is also in agreement. I've updated the latest revision to re-order the toggle switches with v2 selected by default.