Gabor Varadi issues

Results 78 issues of


                                            Gabor Varadi

Consider if a `LocalBackstack` in a navigator should attempt to find a parent `LocalBackstack` and connect itself as a child

See `backstack.setParentServices()` in Simple-Stack 2.8.0 https://github.com/Zhuinden/simple-stack/issues/239

question

design required

Consider if it should be possible to somehow get a reference to the Backstack created in ComposeNavigator

https://github.com/Zhuinden/simple-stack-compose-integration/blob/392aea6d394f04d74cf00cfd7b6f50d04078a488/core/src/main/java/com/zhuinden/simplestackcomposeintegration/core/ComposeNavigator.kt#L27 When nesting, it might make sense to expose the Backstack created in ComposeNavigator, so that a parent can potentially call `goBack()` on it when back is not intercepted automatically....

question

design required

LocalViewModelStoreOwner needs to implement HasDefaultViewModelProviderFactory

Since 2023-02-16, finally, the navigation compose hilt integration no longer asks explicitly for "a ViewModelStoreOwner" and then deliberately ignores it if it's not a NavBackStackEntry, but still expects a `HasDefaultViewModelProviderFactory`...

enhancement

help wanted

critical

design required

[realm-pagination] Consider possibility of moving `open()` and `close()` of pagination manager to the `onActive()` and `onInactive()` of ComputableLiveData

[realm-pagination] Look into possibility of moving only invalidation tracking to handler thread, and keep queries on io() using realm.refresh

enhancement

Support internal class/field names + module field naming policy

Realm 5.0.0+

Gabor Varadi

Consider if a `LocalBackstack` in a navigator should attempt to find a parent `LocalBackstack` and connect itself as a child

Consider if it should be possible to somehow get a reference to the Backstack created in ComposeNavigator

LocalViewModelStoreOwner needs to implement HasDefaultViewModelProviderFactory

Inflation should have a hook which allows it to be async

Unit tests

Dialog state is not properly persisted

[realm-pagination] Upgrade to AAC Paging 1.0-alpha4

[realm-pagination] Consider possibility of moving `open()` and `close()` of pagination manager to the `onActive()` and `onInactive()` of ComputableLiveData

[realm-pagination] Look into possibility of moving only invalidation tracking to handler thread, and keep queries on io() using realm.refresh

Support internal class/field names + module field naming policy