ember-paper: Error using chips on Ember (CLI) 2.13: expected an implementation for 6

Hey, thanks for all the work on this, it’s been helpful for me to have a lot of UI taken care of so I can focus on business logic.

I tried updating an application to Ember 2.13 today and ran into this error in the console, with part of the UI failing to render:

ember.debug.js:19829 Error: expected an implementation for 6

Stacktrace
    at Object.debugAssert [as assert] (ember.debug.js:1498)
    at Compilers.compile (ember.debug.js:1201)
    at compileStatement (ember.debug.js:1200)
    at ember.debug.js:1200
    at Array.forEach (<anonymous>)
    at WrappedBuilder.compile (ember.debug.js:1200)
    at ComponentLayoutBuilder.compile (ember.debug.js:1173)
    at Object.compileLayout (ember.debug.js:1173)
    at Cache._emberMetal.Cache.owner [as func] (ember.debug.js:11330)
    at Cache.get (ember.debug.js:18578)

I tracked it down to this line in my header template:

{{#paper-chips readOnly=true content=chips as |item|}}<span title='{{item.title}}'>{{item.label}}</span>{{/paper-chips}}

I’m admittedly using chips outside their intended purpose, just to show an indicator in the header when you’re viewing a “sandbox” site. I can accomplish this differently without using chips, I was just being lazy about CSS etc.

I’ve removed the use of paper-chips for now but hopefully I’ll find some time to look into this and propose a fix.

My limited investigation has shown me that the failure is unrelated to the block use; even when I changed the template to this it still produced the same error:

{{paper-chips readOnly=true content=chips}}

It’s my belief that this relates to Babel 6, based on the text of the error, but it’s pretty mysterious!

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 17 (8 by maintainers)

Commits related to this issue

Most upvoted comments

FWIW, I am working on those two issues. Hope to have something for the rest of the glimmer team to review tomorrow. Unfortunately, there are some compounding factors in glimmer-vm ATM. Basically, Ember 2.13/2.14 are using glimmer-vm packages at 0.22.x, but master is a significantly different architecture. So any changes we make at this point have to be fixed twice 😭 …

To everyone involved in this fix, thank you!

Confirmed that Ember 2.13.3 resolves this issue (at least when using Chips as in the demo page).

I basically just upgraded to 2.13, hit these issues then dropped back to 2.12 so didn’t get a chance to test it. Still have ember-cli 2.13 though so get ember install with yarn etc which is awesome.

🥇 rwjblue!