-
Data Down / Actions Up
- http://emberjs.jsbin.com/nayaho/edit?html,js - Interdependent select boxes. No observers.
- http://ember-twiddle.com/2d7246875098d0dbb4a4 - One Way Input
-
Plain JSBin's
-
Ember Version Base JSBin's
For starters, just go the /test
directory.
By default you'll see your JSHint validations in the test suite.
Any file that ends with -test.js
will get executed.
Generators also create some tests on your behalf.
So, we actually want to build up and tear down the entire application between tests.
window.addEventListener('error', function(e) { | |
var file = e.filename | |
var line = e.lineno | |
var collumn = e.colno | |
var searchUrl = encodeURIComponent(e.error.message) | |
console.log('Ocorreu um erro no arquivo',file,'na linha',line,':',collumn) | |
console.log('Para buscar o erro, acesso o link :','http://stackoverflow.com/search?q='+searchUrl ) | |
console.log('Powered By :') | |
console.log('%c', 'padding:28px 119px;line-height:100px;background:url(http://cdn.sstatic.net/stackoverflow/img/sprites.png?v=6) no-repeat;'); |
These are the items that we envision should be completed in order for the ember-engines project to get to version 1.0. This list should not imply an order or priority; all of these items need to be completed before the project can be considered ready for 1.0.
The ability to lazily load routed engines has proven to be very useful; we'd like to enable the same capabilities for routeless engines. Some work has already started (see ember-asset-loader issue #56).
These are the tasks to reach that goal:
- write helper
- write accompanying tests