Issue with Ember Data 3.2?

[corrspt]

Hi,

I'm not sure what's happening but on my application I've upgraded Ember to 3.2 and power-select-with-create started behaving weirdly... when I select a value, it will not show in the trigger as the selected value. If I swapped power-select-with-create to a regular power-select things start working as before. (meaning that I can see the value)

I've made a reproduction repo, based on the current master repo of power-select-with-create. It's available here https://github.com/corrspt/ember-power-select-with-create/tree/test-issues.

I'm still trying to setup an Ember Twiddle, but this repo (just navigate to localhost:4200 and you can read the description).

Here's a gif of what happens.

Thanks in advance for any pointers in how to solve this, been struggling with this for the past day 😢

Edit: I've created an Ember-Twiddle for this, The Twiddle is here https://ember-twiddle.com/417bca3fb3b46432ba255a608a56555e.

I couldn't create the Twiddle initially but with the help of cibernox, I was able to. Funny thing, in the twiddle, even power select does not work, while locally it does.... weird. But after a second attempt to setting the value, it seems to work.

Edit2: I've since tried to upgrade to Ember 3.3 and downgrade to Ember 3.1 but with no noticeable effect.

Also, locally I'm running Mac OSX 10.12.6 and Chrome 67.

[corrspt]

Ok, I should have suspected this. duh

So the issue is with Ember Data 3.2. Version 3.1 and below are fine. After I was able to create the twiddle is was easier to experiment and it struck me, maybe I should try another version of Ember Data, and sure enough.... it works. 😓

I'm going to submit another issue in the Ember Data Repository. I'm going to refer this one, but I think you can close it @cibernox. Thank you so much for helping me setup the Twiddle and thanks a lot for the ember-power-* addons.

EDIT: For reference Issue in the Ember Data Repository#5553

[bmfay]

@corrspt I encountered the same problem and was totally stumped (#81). I'm glad you figured it out was Ember Data as downgrading to 3.1 was the only workaround. The response to the Ember Data issue doesn't seem totally hopeful (emberjs/data#5553), but I guess we'll wait and see...

[corrspt]

Hey @bmfay Glad I helped. I did pull a few hairs out while debugging this 😅. I'm hoping that they'll eventually re-open the issue.