SwiftBySundell | Code samples from the Swift by Sundell website & podcast | Audio Utils library

I don’t use SwiftUICharts so I can’t test it, but the least you can try is manually set the id to the view

Let's say you store a flag in UserDefaults to know whether the user has completed onboarding:

Here are possible variants of initializers

You can do it in onAppear of generated content, but I suppose it is better to do it not directly but via binding (which is like a reference to state's external storage), like

I suggest you going out of GeometryReader at this point, and try just use some constants.

Here I'm using UIScreen.main.bounds.size which is device size. And my relative center y is not limited to 0..1 anymore: because we have more items than one screen. Not sure if you need that in your app or you could just use static values for y distance.

Now to the size calculations. Path doesn't act like any other view, it not taking space of its content(in this case points to draw), because you may draw points with location less than zero and more that you need to actually draw.

To apply height modifier to Path I've created heightToFit extension: it receives method which will draw Path(stroke/fill/etc), and after drawing applying height modifier equal to boundingRect.maxY which is bottom point of drawn path

I think you should think about a minor restructure of your code, and use only 1 @StateObject/ObservableObject. Here is a cut down version of your code using only one StateObject source of truth:

Note: AFAIK Binding is meant to be used in View struct not "ordinary" classes.

PS: what is identifiableIndicies?

remove

[cache] capture is still a strong reference to the ImageLoader property but doesn't retain self. And that prolongs the lifetime of just the cache object while a strong reference to cache is held by that request(url) callback block - self can be dealloced even before the callback block is done, and cache can hang around a bit longer.

You only get a retain cycle if there is a loop of strong references A->B and B->A, or A->B->C and C->A etc. Here we have A->Cache and some block that A created but then hands off to url session retains Cache. so that's not a cycle A->Cache and request(url) completion handler also -> Cache. A is free to be dealloced, meaning Cache reference count would go from 2 to 1 and still be around while the url session downloads.

Ideally, instead of passing in an actual instance of UserDefaults, you would instead pass a different type of object that doesn't require that cleanup. A simple example would be something like: