title: Polymer 1.x: Deep link databinding to Firebase
body: <p>I want to databind a <code>settings</code> object to <strong><em>deep links</em></strong> in my Firebase via a <code>firebase-document</code> element as follows:</p>
  
  my-element.html
  
  <pre><code>&lt;firebase-document location="&lt;my-firebase&gt;/users/uid/settings"
                     data="{{settings}}"&lt;/firebase-document&gt;
  ...
  &lt;paper-input label="Name" value="{{settings.name}}"&gt;&lt;/paper-input&gt;
  &lt;paper-input label="Email" value="{{settings.email}}"&gt;&lt;/paper-input&gt;
  ...
  settings: {
    type: Object,
    notify: true,
    value: {},
  ...
  </code></pre>
  
  <p>When I enter values in the <code>paper-input</code> fields in my app for <code>name</code> and <code>email</code>, I expect to see the Firebase values update. But, instead, they do not update.</p>
  
  <p>What is the <strong><em>best-practice</em></strong> method to accomplish this deep-link databinding?</p>
  
  <h3>Edit</h3>
  
  <p><a href="https://github.com/GoogleWebComponents/firebase-element/issues" rel="nofollow">I just noticed there are 35 open issues with the <code>firebase-element</code></a> and <a href="https://codelabs.developers.google.com/codelabs/polymer-firebase/index.html?index=..%2F..%2Findex#4" rel="nofollow">this codelab appears to bypass using it for the same reasons</a>. If the element isn't fully ready yet, please just state that. Also, the imports seem unusual <a href="https://github.com/GoogleWebComponents/firebase-element" rel="nofollow">based on the language here</a>:</p>
  
  <blockquote>
    <p>Components that want to use firebase should depend on firebase-element and import firebase.html to be safe from library duplication. Such components need not use Polymer or firebase-element, but we put the import and the element in one package for convenience.</p>
  </blockquote>
  
  <p>It's hard to understand what the above paragraph is trying to say. So an example would help.</p>