@FetchRequest not refreshing

I have got it working now but for what feel like all of the wrong reasons.

I moved the notification handler up a level, so that the view that contains all of the @FetchRequest is force refreshed by being re-constructed.

The solution feels dirty, I still beleive that the @FetchRequest should be able to trigger a data reload itself when the data changes.

The top level ContentView is now having to be very heavy handed IMHO. by:

struct ContentView: View {
    private var didUpdate = NotificationCenter.default.publisher(for: .coreDataRemoteChange)
    @State private var renderID = UUID()
    var body: some View {
        NavigationView {
            MasterListView()
                .navigationBarTitle(Text("Things"))
                .navigationBarItems(
                    trailing: EditButton()
                )
            Text("No Content").noContentStyle()
            Print("ContentView \(renderID)")
        }
        .id(self.renderID)         
        .onReceive(self.didUpdate) { _ in
            print("ContentView received .coreDataRemoteChange")
            self.renderID = UUID()
        }
        .navigationViewStyle(DoubleColumnNavigationViewStyle())
        .accentColor(.accent)
    }
}

... attaching a UUID to the NavigationView.

Because the notification is reliable and the data was actually being updated, techniques like

NSManagedObjectContext.mergeChanges(fromRemoteContextSave: [NSInsertedObjectsKey: addedThings], into: [taskContext])

are not actually required.

I would be surprised if this was the way we are intended to use @FetchRequest

Code Block 
viewContext.automaticallyMergesChangesFromParent = true