Discontinued

Summary Improve computed property syntax Motivation Today, the setter variant of CP's is both confusing, and looks scary as sin. (Too many concepts must be taught and it is too easy to screw it up.) Detailed design today: fullName: Ember.computed('firstName', 'lastName', function(key, value) { if (arguments.length > 1) { var names = value.split(' '); this.setProperties({ firstName: names[0], lastName: names[1] }); return value; } return this.get('firstName') + ' ' + this.get('lastName'); }); Tomorrow: fullName: Ember.computed('firstName', 'lastName', { get: function(keyName) { return this.get('firstName') + ' ' + this.get('lastName'); }, set: function(keyName, fullName, oldValue) { var names = fullName.split(' '); this.setProperties(...

The Road to Ember 2.0 Intro Today, we're announcing our plan for Ember 2.0. While the major version bump gives us the opportunity to simplify the framework in ways that require breaking changes, we are designing Ember 2.0 with migration in mind. This is not a big-bang rewrite; we will continue development on the master branch, and roll out changes incrementally on the 1.x release train. The 2.0.0 release will simply remove features that have been deprecated between now and then. Our goal is that you can move your Ember app to...

Summary Solicit feedback about the support timeframe for Internet Explorer 8 and Internet Explorer 9. Motivation As Ember heads towards version 2.0, it is a good time to evaluate our browser support matrix. Ember follows Semantic Versioning, and we consider browser compatibility to be under the umbrella of those guarantees. In other words, we will continue to support whatever browsers we officially support in Ember 2.0 until Ember 3.0. Ember 1.x did not have an official browser support matrix, but we would like to correct this for Ember 2.0. We want to make this decision...

Summary This RFC outlines a new strategy for the registration of helpers in Ember 1.13. In previous versions of Ember, helper lookup was a two-phase process of: Look in a whitelist of registered helpers. If in the whitelist, resolve that path in the container. If the path has a dash, try to resolve it in the container If the container does not have a factory for this path, treat the path as a bound value. This logic runs for every {{somePath}} in an Ember application. This proposal attempts to simplify and unify that logic in a a single...

Summary Replace PhantomJS with Firefox as the default browser for continuous integration testing. Motivation We want to provide the best possible out-of-the-box continuous integration testing experience for Ember apps. Today that means shipping with configurations for testem and TravisCI. Those configurations use PhantomJS. But PhantomJS is a weird environment. Users must often fix Phantom-specific browser bugs, which is wasted effort since real users never run your app in Phantom. And "how to debug in Phantom" is an entire extra skill people are forced to learn. A user-targeted, standards-compliant, modern browser makes a better default...

Summary Add https://github.com/rwjblue/ember-cli-template-lint as a default addon for the app and addon blueprints using the recommended rules. Motivation Linting and security in templates would help not only individual developers write better apps with better accessibility and security, but would also help teams to be on the same page and stick to a handful of standards. Detailed design Move ember-cli-template-lint to the ember-cli org (better for contributing and getting work off one person, @rwjblue) Add the dependency to the app blueprint here: https://github.com/ember-cli/ember-cli/blob/...

EmberData | Deprecate ajax requests Summary Deprecates use of ajax methods in favor of fetch to request API data. Motivation Currently, ember-data maintains two methods for users to fetch data from their backend - fetching with jQuery.ajax and fetch. Confusion further exists in the adapters if users implement functionality to change out of the box behaviour. They can override ajax methods but without a clean interface to operate with, what they really may be doing is overriding how fetch works. With Ember 4.0 dropping jQuery, we should take a hard stance on dropping the use of ajax in the...