Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Calling $save does not trigger a $watch event
See original GitHub issueWhen we call $save on a local object, we push the current value to the server. If a change occurs, then a child_changed event will be triggered. However, because the data will already be set locally, no change will occur, and therefore neither $FirebaseArray nor $FirebaseObject will trigger a $watch event after. Consider sending notifications for these?
Issue Analytics
- State:
- Created 9 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Saving changes does not trigger watchers. Saving same file in ...
Problem: While running the watcher program, saving files in Visual Studio does not trigger the watcher to rebuild assets.
Read more >Ability to disable/not trigger watch handler on data? #1829
It seems that trying to undefine the handler while making the operation doesn't work.
Read more >How to watch prop even if it does not change? - Stack Overflow
I have watcher with the same name as a prop. The prop is dynamically set in a parent component on some event. I...
Read more >Events | Google Calendar
Property name Value Notes
anyoneCanAddSelf boolean writable
attachments list
attachments.fileId string
Read more >Creating a CloudWatch Events Rule That Triggers on an AWS ...
To create a rule that triggers on an action by an AWS service that does not emit events, you can base the rule...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@jaymanned please post your own issue, rather than replying to one closed 2 years ago.
This has been fixed since version 0.8.1. See the last item in the 0.8.1 changelog.