Skip to content

Instantly share code, notes, and snippets.

@ssoroka
Last active December 18, 2015 18:19
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save ssoroka/5824696 to your computer and use it in GitHub Desktop.
Save ssoroka/5824696 to your computer and use it in GitHub Desktop.
Ember issues.

ember issues

  • update docs that use {{#each controller}} to {{#each model}} and/or explain the difference.
  • assert errors or log debug info when templates reference undefined attributes in development
  • need larger project examples of ember in live use for a production application. docs are inconsistent and too shallow on scope
  • Horrible gotchya: Passing a second argument to {{render}} creates a new controller (like {{control}} would) rather than reusing the existing one (without warning or documentation). This makes perfect sense once you understand it, but there's no indication that this is happening except that properties you set on the controller are missing. I'd love a developer mode that tells you everything Ember is generating silently for you (controllers, routes, new instances, missing attributes, etc)
  • defining a route with nothing in it is not the same as the auto generated one (it overwrites the default setupController or model?). No ideas why.
  • attributes absolutely need a readOnly option. eg: createdAt: DS.attr 'date', readOnly: true. Control over formatting how data is received from and serialized to the server in ember-data would make it a ton easier to consume apis you don't have direct control over.
  • an App.loaded(function(){ .. }) construct would prevent race conditions between defining models and using them (ran in to this in jsbin)
  • lack of native fields (like radio buttons) is frustrating.
  • inconsistent: templates are rendered with folder.name but partials are required as "folder/name"

Ember-data issues

  • setting a belongsTo field's id to a value writes nothing to the server on POST.
  • 'date' attributes on ember-data models do not complain when you pass in strings or integers representing dates (even though Ember.Date.parse returns an integer date). It then silently serializes a null to the server.
  • There's no way to post back to a nested resource path. POST to /blogs/3/posts/6/comments ? Nope; can't do that.
  • docs don't reference "then", but it's required for an app of any significant size
  • relations don't seem to work.
@wagenet
Copy link

wagenet commented Jan 30, 2014

@ssoroka, this gist is 7 months old which means it was written before Ember 1.0. Many of these items have been improved and the others we're aware of. I'd like to try to give you a more detailed breakdown of what exactly we've done and what remains to be done but it may take a little while.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment