Scope the dependency to a navigation graph

[BenderNK]

I created a dependency called LocationManager by following the documentation in this library. It works great - no problems there. However, I would like to scope this dependency to a part of the navigation graph so that when I go back to a place where I don't need the said location manager anymore, i would like to release it from memory. I looked around but I couldn't find a way to configure the dependency this way. If there is already one and I missed that, apologies in advance. I took a snapshot of my memory graph where I would like no longer see LocationManager. However, CachedValues object still retains a reference to this dependency. Is this feasible? Check out the following screenshot.

[rhysm94]

This can work, but you need to "bake in" the ability to create and destroy the dependency within your own code.
Maybe you could keep a NoOpLocationManager/UnimplementedLocationManager as the default value in a LockIsolated, and then call a method on your dependency like this:

@Dependency(\.locationManager) var locationManager
locationManager.create()

where create (and destroy) looks something like this:

static var liveValue: Self {
  let locationManager = LockIsolated<LiveLocationManager>(.noOp)

  return Self(
    create: {
      locationManager.withValue { manager in
        manager = .live
      }
    },
    destroy: {
      locationManager.withValue { manager in
        manager = .noOp
      }
    }

[BenderNK]

Thanks for the advice. I will implement this in our project and let you know - about a week or so from now.