Open rwjblue opened 7 years ago
My large concern is that these can't be cached, and we don't have any kind of fingerprinting in the backend.
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?
When choosing
canary
/beta
/release
as the Ember version for a newly created twiddle, an error is displayed. This started once https://github.com/ember-cli/ember-twiddle/pull/532 was deployed. The work around is to moveember-data
out ofaddons
and intodependencies
(in thetwiddle.json
).As of https://github.com/ember-cli/ember-twiddle/pull/532
ember-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.I have taken a crack at working on that in https://github.com/joostdevries/twiddle-backend/pull/27, but really need @joostdevries' and @Gaurav0's advice there to ensure we aren't shooting ourselves in the foot.