Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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.

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

touch$ behaviour #80

Closed
mnmaltsev opened this issue Feb 24, 2021 · 2 comments
Closed

touch$ behaviour #80

mnmaltsev opened this issue Feb 24, 2021 · 2 comments

Comments

@mnmaltsev
Copy link

mnmaltsev commented Feb 24, 2021

I'm submitting a...


[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Performance issue
[x] Feature request
[ ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:

Current behavior

Currently touch$ emits distincted value.

Expected behavior

touch$ should emit value on every touch/untouch control events

What is the motivation / use case for changing the behavior?

New added controls linked to lead control touch$ not receive touch events after first lead control touch event.

@NetanelBasal
Copy link
Member

Can you provide a code example, please?

@mnmaltsev
Copy link
Author

repro:
https://stackblitz.com/edit/angular-ivy-e81zmg?file=src%2Fapp%2Fapp.component.html

this behaviour reason:

readonly touch$ = this.touchChanges.asObservable().pipe(distinctUntilChanged());

@ngneat ngneat locked and limited conversation to collaborators Jun 10, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants