Comments (5)
Am I correct in thinking that once unregistered, the service is destroyed and that instance won't ever be reused?
Back in Simple-Stack 1.x there was a "bug" (design oversight) caused by how re-registering the same instance would call onEnterScope()
to run multiple times, 2,x exists specifically because this section was heavily reworked to ensure that 1 object is tracked only once per registration.
So even if the same instance is added in multiple scopes, it would only have onServiceRegistered
called when 0 -> 1
, and onServiceUnregistered()
only called when 1 -> 0
, but not later.
Therefore, unless you cache these poor objects in some singleton and "re-add the same instance" again, then these callbacks are ensured to be only called once. If the object is instantiated along with the scope as is done in the samples in bindServices()
, then they are definitely only called once.
TL;DR:
Am I correct in thinking that once unregistered, the service is destroyed and that instance won't ever be reused? So onServiceRegistered and onServiceUnregistered only ever get called once each?
Yes
Another question; with Jetpack ViewModel, I often have a loadInitialData() method that I call from Fragment.onViewCreated, because I'd rather not kick off database calls/network calls from the constructor, it feels hacky and is not nice for testing. onServiceRegistered looks ideal for kicking off initial data loading, would you recommend that?
Yes
😉
btw, if the class is instantiated "from a scope" as it would happen from a Backstack, then onServiceRegistered
and co. is invoked by Backstack normally. All unit tests in simple-stack are unit tests, so all scoping logic and "scoped service lifecycle management" is unit-testable.
from simple-stack.
Okay, that's helpful thank you. Want me to make a PR to add that info onto onServiceRegistered
/onServiceUnregistered
?
from simple-stack.
Hmm, there is already a comment like so:
/**
* When a service implements {@link Registered}, then it will receive a callback when the service has been registered to at least one scope.
*/
public static interface Registered {
/**
* Called when the service has been registered to any scopes, and this is the first scope it was registered to.
*/
void onServiceRegistered();
/**
* Called when the service is no longer registered in any scopes.
*/
void onServiceUnregistered();
}
Although if it's not actually lcear, then it can be useful. It also doesn't really mention how onServiceRegisterd
runs after fromBundle
.
from simple-stack.
I will consider this solved.
from simple-stack.
Sorry I didn't get back to you, yeah I think it's fine
from simple-stack.
Related Issues (20)
- Can I Use @styles/Theme.MyComposeTheme on AndroidManifests.xml? HOT 3
- Question: What is the purpose of RegistrationViewModel inside ServiceProvider in extension-compose-example? HOT 4
- What is the proper way to add a key to the top even if it already exists in the backstack? HOT 2
- Publish to MavenCentral instead of just Jitpack.io
- Unable to start activity ComponentInfo{com.xxxxxxxxxx.yyyyyy/com.xxxxxxxxxx.yyyyyy.activities.MainActivity}: androidx.fragment.app.Fragment$InstantiationException: Unable to instantiate fragment q2.v1: could not find Fragment constructor HOT 7
- How to 'lookup<>()' scoped class from an Android Service HOT 2
- Lazy initialization of ScopedServices HOT 2
- KMM support? HOT 2
- Screen can get the service from wrong scope during back animation HOT 6
- Backstack is not available in a child Fragment's onCreate after process death
- DialogFragment and BottomDialogFragment as part of navigation stack, question HOT 2
- Verify that the new `setParentServices()`'s `lookupFromScope(..., EXPLICIT)` behavior is what is expected
- Updating the Compose example to Compose 1.5.0 requires AGP 8.1
- Should Simple Stack be used in new projects HOT 14
- Crash due to activity.onBackPressed() when removing fragment hosting a WebView in AndroidView {} + FADE HOT 15
- Backstack with espresso HOT 3
- The service does not exist in any accessible scopes HOT 11
- Up navigation examples are hard to find HOT 3
- Consider adding Backstack.services() method as in GlobalServices.services() HOT 4
- Extensions should support Fragment in-app predictive back animations
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from simple-stack.