-
Notifications
You must be signed in to change notification settings - Fork 263
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
Avoid infinite render on value change #524
Conversation
We had to roll this back, due to #484. Any thoughts on how to fix the render + not break acceptance tests? |
I had not seen that issue thanks for linking. One thing I am having trouble understanding is why we are not just returning _fetch(ref) {
return ref.once('value');
} |
I have added a test which connects to a live firebase since that seems to be where the run loop issues were coming from. This test failed as expected with my initial commit, and now passes when only returning the promise from |
addon/adapters/firebase.js
Outdated
}); | ||
|
||
}, log); | ||
return ref.once('value'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The log
input param is not used. Try this:
return Promise.resolve(ref.once('value'), log);
Ok updated. Let me know if you want to squash this down to one commit. |
We can squash from the pull request. Tests are red though @steven-ferguson can you take a peek? |
I was not able to reproduce the failures on my local machine. Would you mind kicking the build off again? |
I kicked it off again, let's see how that goes. |
Pushing out a release, btw. |
Fixes #480 . Looks like the issue was closed even though a fix was never merged.