Package-level declarations
Types
Object that provides access to a BoomerangStore in Jetpack Compose. This is the main entry point for accessing a BoomerangStore in a Compose UI.
Functions
A Composable function that provides a BoomerangStore from an Activity that implements BoomerangStoreHost to its content. This function retrieves the BoomerangStore from the hosting Activity and makes it available to the content via LocalBoomerangStore. This function should be used when your app uses both Composables and Fragments for navigation. For more info check BoomerangStoreHost.
A Composable effect that tries to catch a boomerang value from the BoomerangStore when a specific lifecycle event occurs. This effect is typically used to process data that was stored in the BoomerangStore when the UI becomes visible. Example usage
A specialized Composable effect for catching event notifications from the BoomerangStore. This is a convenience function that simplifies catching events in Compose UI.
A Composable function that creates a custom BoomerangStore and provides it to its content via LocalBoomerangStore. The store is saved and restored across configuration changes using rememberSaveable with a custom saver. This function is useful when you want to use a custom implementation of BoomerangStore instead of the default one. It should be used on the top-level of your Compose application before creating Navigation components.
A Composable function that creates a DefaultBoomerangStore and provides it to its content via LocalBoomerangStore. The store is saved and restored across configuration changes using rememberSaveable with a custom saver. This function is useful when you have fully Composable navigation. It should be used on the top-level of your Compose application before creating Navigation components (f.e. before calling NavHost in Jetpack Navigation). Example usage
A Composable effect that tries to catch a boomerang value from the BoomerangStore when a specific lifecycle event occurs. This is an inline version that accepts a lambda function instead of a BoomerangCatcher. This effect is typically used to process data that was stored in the BoomerangStore when the UI becomes visible. Example usage
Android-specific implementation of rememberBoomerangStore.
Remembers a BoomerangStore across recompositions and configuration changes. This function is implemented differently on each platform to ensure proper state saving and restoration.
Desktop-specific implementation of rememberBoomerangStore.
iOS-specific implementation of rememberBoomerangStore.