Gordon L. Hempton

Something fishy with repl tests

2

Looking over `test/repl.coffee` I am noticing some strange things. The first test: ``` testRepl 'starts with coffee prompt', (input, output) -> eq 'coffee> ', output.lastWrite 1 ``` Shouldn't that be...

``` Logging.backtrace = true # somewhere inside a controller raise StandardError.new("errorz") ``` After some prying, the `format_obj` gets a string representation instead of the raw exception. I assume Rails processes...

Add `session.persist`

1

This method would create or update a model immediately on the server. The perk of this over a normal `session.flush` is that it could take advantage of the underlying opts...

E.g.: ``` @on init reset: -> ```

Object function toString() { [native code] } has no method 'set'

``` coffeescript myProp: ~> @get('someOtherProp') ``` Results in ``` javascript myProp: Ember.computed(function() { return this.get('someOtherProp'); }).property(''); ```