4cb18965c9
When setting duplicate as current, batch save original profile and duplicate in a single call via profilesToSave. This is to avoid a double call to willUpdateProfiles() when saving Core Data context. In order to set current profile to one that has not been persisted yet (the duplicate), we need to resort to a pendingProfiles map where to look the duplicate up when setting currentProfileId. Either way, iOS 14 cannot handle updating a "hot" change in a presented NavigationLink. Changing currentProfileId binding while in ProfileView messes up navigation completely (multiple push and pop events). Avoid. |
||
|---|---|---|
| .. | ||
| App | ||
| Shared | ||
| Tunnel | ||