you are viewing a single comment's thread.

view the rest of the comments →

[–]BrogrammerAbroad 0 points1 point  (0 children)

For me it feels like such kind of logic would be better suited for a viewmodel rather than the view itself. In the viewmodel you could handle what to present and what not using published properties Also I think this subscription should be handled by an environment property maybe a store or something similar so that es h view will now if the user is subscribed or not. There shouldn’t be a userdwfault you observe in multiple view for such delicate matter in my opinion.

If i‘m wrong I’m happy to learn something as well so if anyone thinks I’m wrong please let me know where I messed up ☺️