if I have a NavDrawer whose content is largely dyn...
# compose
j
if I have a NavDrawer whose content is largely dynamic (let's say 75% of the items in it come from our API), is it a reasonable thing to do to create a ViewModel for the drawer itself? most of the code I've seen demonstrating NavDrawers in Compose all have static hardcoded items, but my use case requires dynamic content and it feels right to have a NavDrawerViewModel to manage it. does this seem like a good idea?
m
Absolutely. This is what view models are intended for.