You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When choosing canary / beta / release as the Ember version for a newly created twiddle, an error is displayed. This started once #532 was deployed. The work around is to move ember-data out of addons and into dependencies (in the twiddle.json).
As of #532ember-data is now consumed as an addon. This leverages the addon builder backend to build the addon for the specific Ember version. Unfortunately, the addon builder does not currently support building for the various Ember release channels.
Since this has been open for such a long time without a solution and is a common problem that doesn't even have any visual feedback to the user, what do you think about removing the options that do not work from the user interface?
Activity
Gaurav0 commentedon Jan 31, 2018
My large concern is that these can't be cached, and we don't have any kind of fingerprinting in the backend.
urbany commentedon Jul 27, 2018
Since this has been open for such a long time without a solution and is a common problem that doesn't even have any visual feedback to the user, what do you think about removing the options that do not work from the user interface?