[Office Hours] How to properly access Spezi Modules

[kkellybonilla]

Related Discussion

Hi! I'm working on the Stanford360 app, and I'm currently trying to connect the PatientManager module to all model managers in the app (activity, hydration, protein) such that our new DashboardView properly reflects the app state as its updated in its respective views (e.g. logging water intake updates both the hydration and dashboard view).

I was able to do this pretty easily for the hydration view since I just had to access the PatientManager from the environment; however, for the activity view, I need to access the PatientManager within the ActivityManager, which is not a view. Thus, I would need to use the @Dependency modifier; however, I get the following error when doing so:

Unknown attribute 'Dependency'

I believe this is because ActivityManager is not currently a Spezi Module. Is there another way to access the PatientManager within the ActivityManger, or would the best approach be to make our ActivityManager (and all managers for that matter) Spezi Modules?

Reproduction

1. Clone the Stanford360 Repo
2. Checkout and pull this branch
3. Navigate to the following path to see the error: Stanford360/Activity/Model/ActivityModels/ActivityManager

Additional context

No response

Code of Conduct

• I agree to follow this course's Code of Conduct and Contributing Guidelines

[shamit05]

Could you perhaps try creating the patientmanager as just a regular variable and then passing in the patientmanager in the init function of ActivityManager when calling it from the view?

So set it as this:

 private var patientManager: PatientManager

And then in init:

init(healthKitManager: HealthKitManager = HealthKitManager(), patientManager: PatientManager) {
       self.healthKitManager = healthKitManager
       self.patientManager = patientManager
       loadFromStorage()
       setupHealthKit()
   }
   ```

[kkellybonilla]

I don't know if I understand how this will work. the PatientManager must be the same across the app, if I initialize a new PatientManager it would have an entirely different patient associated with it

[kkellybonilla]

I was able to make the ActivityManager a module and access the PatientManager with the dependency modifier; however, i still get an error saying that it accessed a module before it was initialized (despite them all being initialized in the app delegate configuration method

[PSchmiedmayer]

@kkellybonilla Great to hear that you could access the module using the dependency modifier. Please be aware that you can only access them after the initialization when the configure method has been called; when do you currently aim to access the PatientManager?