Michel Feinstein
Michel Feinstein
I agree it's better than what we have now, but once this lands, we won't be changing it any time soon, so I rather have it covering as many cases...
I prefer enums too. Just to add a bit more info, I usually use a user stream in my apps. Whenever there's a change in login state, the stream emits...
I know, I don't disagree with this, my point is more about if we can make it better and remove this control from the devs. It's very hard to manage...
Sure, I just changed the app name here: ```groovy buildscript { repositories { mavenCentral() } } plugins { id "com.android.application" // START: FlutterFire Configuration id 'com.google.gms.google-services' // END: FlutterFire Configuration...
I think so, have you released any fixes?
@grouma can your example be used for `Stream`? @natebosch yeah, I see your point, it does fill a bit of an antipattern, but at the same time `doesNotEmitFor(Duration)` sounds useful...
@grouma thanks, but for my use case, @natebosch solution was better as I had to call a method to trigger the emission.
I opened this 3 years ago: https://youtrack.jetbrains.com/issue/IDEA-328407/Add-breakpoint-selection-for-nested-lambdas-just-like-Java-has The UI has changed ever since: https://www.jetbrains.com/help/idea/using-breakpoints.html#set-line-breakpoint It would be great if we could prioritize this
Hi @alexander-doroshko, how could we help to prioritize this so you could investigate the feasibility for this feature?
@pingbird so how active installs should proceed?