Firebase: Priority set to null on server but not on client when setting grandchild -


to reproduce, check out http://jsfiddle.net/3ar7n/16/ . first click "set child , grandchild," sets child priority , sets grandchild within it. click "show local values" , you'll see child still seems have priority of 123. click many times - priority comes 123.

once you're satisfied local priority 123, refresh whole page. you'll dismayed see priority null.

i can believe concurrency issue, effects of set happening in different orders. expected behavior setting child clear priority of parent?

thanks easy test case! indeed bug. client , server handling case differently, why you're seeing inconsistent behavior.

note occurs if "setwithpriority" primitive value, , write deeper in tree (which deletes primitive value).

update: has been fixed.


Comments

Popular posts from this blog

php - Wordpress website dashboard page or post editor content is not showing but front end data is showing properly -

How to get the ip address of VM and use it to configure SSH connection dynamically in Ansible -

javascript - Get parameter of GET request -