ef4 / ember-elsewhere

Render elsewhere in the DOM, with nice composition, animation, etc. Based on 100% public API.
MIT License
184 stars 25 forks source link

I think my setup sometimes has a double render error #18

Open NullVoxPopuli opened 7 years ago

NullVoxPopuli commented 7 years ago

route A/ route A.B / route A.B.C /

each of those routes calls to-elsewhere with the same name, and this might be causing

Assertion Failed: You modified "service.actives" twice on <aeonvera@service:ember-elsewhere::ember853> in a single render. It was rendered in "component:from-elsewhere" and modified in "component:paper-sidenav-container". This was unreliable and slow in Ember 1.x and is no longer supported. See https://github.com/emberjs/ember.js/issues/13948 for more details.

my from-elsewhere looks like this:

{{#paper-sidenav-container}}
  {{#if showSidebar}}
    {{#paper-sidenav open=leftBarOpen class='md-whiteframe-z2' onToggle=(action (mut leftBarOpen))}}
      {{from-elsewhere name='left-side-bar'}}
    {{/paper-sidenav}}
  {{/if}}

and each of my to-elsewhere's look something like this:

{{to-elsewhere named='left-side-bar'
  send=(component 'app-nav/event-registration-edit-sidebar'
        event=model.event
       )}}

does anything obviously stick out as bad?