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.

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

Having issue with getterThrottle #3

Closed
3cp opened this issue May 25, 2018 · 2 comments
Closed

Having issue with getterThrottle #3

3cp opened this issue May 25, 2018 · 2 comments

Comments

@3cp
Copy link
Member

3cp commented May 25, 2018

Having issue with using @getterThrottle in a component using dnd (probably only affect usage of events like 'dnd:didEnd').

aurelia-event-aggregator calls subscribers synchronously (no setTimeout), but somehow aurelia rendering started too early (before the callback of 'dnd:didEnd' subscribers), which triggered @getterThrottle to cache value in wrong state.

Maybe it's not rendering started too early, it's some mutation in dndDrop triggered some observers which fire getter evaluation immediately (without using queueMicroTask ?!).

Need more investigation.

@3cp
Copy link
Member Author

3cp commented May 25, 2018

Could because of using @bindable to propagate a mutation by 'dnd:didEnd' callback.
@bindable propagation is not immediate I guess.

@3cp
Copy link
Member Author

3cp commented May 25, 2018

Not an issue of dnd itself, but an issue of getterThrottle, aurelia-contrib/aurelia-getter-throttle#1.

@3cp 3cp closed this as completed May 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant