andrzejkrzywda

// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console

andrzejkrzywda

Here is my solution, based on use-cases and AOP.

1. you need to separate persistence from your domain
2. you need to have a proper use-case, not a single request-class, like above.
3. notifications are notifications (twitter, fb), they are implemented with AOP
4. spam detection and language detection are separated (discussable) with an aspect.
5. there is an "app" object that wraps it all together.

The first file is the original example. The second file is mine.

andrzejkrzywda

require 'test/unit'

class KeyTest < Test::Unit::TestCase
  def test_key
    object = Object.new
    assert_equal(:submit, object_key(object))

    def object.persisted?; true end 
    assert_equal(:update, object_key(object))