Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

rx-stateful: not emitting subsequent values - staying in suspense state #111

Closed
michaelbe812 opened this issue May 30, 2024 · 0 comments
Closed

rx-stateful: not emitting subsequent values - staying in suspense state #111

michaelbe812 opened this issue May 30, 2024 · 0 comments
Labels
bug Something isn't working {} rx-stateful

Comments

@michaelbe812
Copy link
Owner

michaelbe812 commented May 30, 2024 •
edited
Loading

Version 1.7.0

Following code does not emit subsequent states:

delete(sourceTrigger: Observable<any>){
 return rxStateful$(param => http.whatever(param), {sourceTrigger})
}
@michaelbe812 michaelbe812 added bug Something isn't working {} rx-stateful labels May 30, 2024
@michaelbe812 michaelbe812 changed the title rx-stateful rx-stateful: not emitting subsequent values - staying in suspense state May 30, 2024
michaelbe812 added a commit that referenced this issue Jul 26, 2024
@michaelbe812
#111 fix(rx-stateful): fix that initially refresh trigger and sharedS…
7355776 
…ource$ emit multiple values
michaelbe812 added a commit that referenced this issue Jul 26, 2024
@michaelbe812
#111 fix(rx-stateful): fix not emitting subsequent values
427d098 
The issue was caused when a source does not emit a thruthy value. This is e.g. the case for Endpoints which send an empty response back, e.g. after a delete-operation.

The problem can easiliy be simulated by
```ts
rxStateful$(
 timer(1000).pipe(switchMap(() => of(null)))
)
```
michaelbe812 added a commit that referenced this issue Jul 26, 2024
@michaelbe812
Bugfix/rx stateful no subs values (#112)
034ce71 
* #111 fix(rx-stateful): fix not emitting subsequent values

The issue was caused when a source does not emit a thruthy value. This is e.g. the case for Endpoints which send an empty response back, e.g. after a delete-operation.

The problem can easiliy be simulated by
```ts
rxStateful$(
 timer(1000).pipe(switchMap(() => of(null)))
)
```

* chore: ehnance demos
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working {} rx-stateful
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@michaelbe812