Working on a SwiftUI App with hierarchical data displayed in split views (primary, supplementary and secondary views).
Since the data is hierarchical across three views, the UI selections that need to be stored in the @SceneStorage is dependent on each other . The primary view user state drives the relevancy of the user state in the supplementary and secondary views.
But loading of the Primary view is predicated on a @FetchRequest, which gets constructed before the view self is instantiated, is predicated on the mailboxID stored in the @SceneStorage. Since the @SceneStorage is limited to be used only within a view...how can one send a parameter to the Predicate in the @FetchRequest which is loaded even before the view is instantiated ?
I am inclined to believe my understanding is wrong but in reality I am facing this interdependency conflict between @SceneStorage and @FetchRequest Lifecycles :(
Note: If I store this attributed are stored in @AppStorage instead of SceneStorage, this is easily resolved because @AppStorage can be invoked to access the parameters even in Non-View classes and hence not tied to view instantiation to be complete.
Any suggestions are deeply appreciated?
Since the data is hierarchical across three views, the UI selections that need to be stored in the @SceneStorage is dependent on each other . The primary view user state drives the relevancy of the user state in the supplementary and secondary views.
But loading of the Primary view is predicated on a @FetchRequest, which gets constructed before the view self is instantiated, is predicated on the mailboxID stored in the @SceneStorage. Since the @SceneStorage is limited to be used only within a view...how can one send a parameter to the Predicate in the @FetchRequest which is loaded even before the view is instantiated ?
I am inclined to believe my understanding is wrong but in reality I am facing this interdependency conflict between @SceneStorage and @FetchRequest Lifecycles :(
Note: If I store this attributed are stored in @AppStorage instead of SceneStorage, this is easily resolved because @AppStorage can be invoked to access the parameters even in Non-View classes and hence not tied to view instantiation to be complete.
Any suggestions are deeply appreciated?