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

getStoredValue attempts to resolve a duplicated/incorrect path #32

Closed
43081j opened this issue Jun 7, 2016 · 3 comments · Fixed by #54
Closed

getStoredValue attempts to resolve a duplicated/incorrect path #32

43081j opened this issue Jun 7, 2016 · 3 comments · Fixed by #54
Assignees

Comments

@43081j
Copy link
Contributor

43081j commented Jun 7, 2016

I'm not sure if this is a bug or expected behaviour, but say I have the following:

<firebase-document path="/foo" data="{{foo}}"></firebase-document>

This works fine, as expected. However, I noticed that getStoredValue is hit in a strange way.

You can see it calls this.ref.child(path). In my case, path is /foo but this.ref is already xyz.firebaseio.com/foo so it tries to resolve /foo/foo. Surprisingly, this doesn't seem to affect anything, foo is still set correctly, but it definitely looks wrong still.

@mraerino
Copy link

May have connections to #18

@Mayhem50
Copy link

I see the same behavior. My ref is set to path so call this.ref.child(path) calls foo/foo. Unlike 43081j, it doesn't work fine for me. To resolve it I had to remove .child(path)

@e111077
Copy link
Collaborator

e111077 commented Jun 15, 2016

It seems as if the code is duplicating the path. The listener callback returns null every time on initialization.

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

Successfully merging a pull request may close this issue.

4 participants