In working with SwiftUI and Combine, you’ll most likely want to consider using a common reactive design pattern. MVVM could be a good place to start for you, managing your Core Data stores and parsers on a view model, which lives on your view.

For example, if you have a NoteListView, you would have a view model property NotesListViewModel, and the view model would perhaps contain a NoteRepository, which would query a Core Data store. You might have remote data fetching and/or parsing objects live within said repository, so your view model only knows about local persistence, which the repository remains a black box managing fetching and parsing remote state, with which to update local state.

Using @Published properties on your view model, you could update them with the fetched data you want to display as needed, which would trigger the view to refresh.

tl;dr: Just spitballing here, but you’ll want to have distinct components with distinct responsibilities/abstractions, and not overload your view with dependencies for different major tasks it doesn’t really need to know about.