Submitting hw2

lib/desugaring.rb

@@ -21,7 +21,9 @@ def all_the_sugar(recipients, event, message)
   # Copy the contents of the previous method here and remove this sugar.
   #
   def desugared_poetry(recipients, event, message)
-    implement_me!
+    mail(message,
+      to: recipients.map(&:email),
+      subject: "You’re invited to #{event.title} on #{event.date}")
   end
 
   # Ruby allows you to pass arguments identified by name instead of just by position. They are really just
@@ -36,7 +38,9 @@ def desugared_poetry(recipients, event, message)
   # Copy the contents of the previous method here and remove this sugar.
   #
   def desugared_named_args(recipients, event, message)
-    implement_me!
+    mail(message, {
+      to: recipients.map(&:email),
+      subject: "You’re invited to #{event.title} on #{event.date}"})
   end
 
   # Ruby’s general syntax for hashes is `{key => value, key => value, ...}`. Because it is so common to use
@@ -51,7 +55,9 @@ def desugared_named_args(recipients, event, message)
   # Copy the contents of the previous method here and remove this sugar.
   #
   def desugared_symbol_keys(recipients, event, message)
-    implement_me!
+    mail(message, {
+      :to => recipients.map(&:email),
+      :subject => "You’re invited to #{event.title} on #{event.date}"})
   end
 
   # You may be wondering how `map(&:email)` works. When you precede the last argument of a method call with
@@ -70,7 +76,9 @@ def desugared_symbol_keys(recipients, event, message)
   # Copy the contents of the previous method here and remove this sugar.
   #
   def desugared_attr_proc(recipients, event, message)
-    implement_me!
+    mail(message, {
+      :to => recipients.map { |x| x.email },
+      :subject => "You’re invited to #{event.title} on #{event.date}"})
   end
 
   # You may recall from the Ruby koans that when you put `#{something}` in a `"`-delimited string, Ruby will
@@ -88,7 +96,9 @@ def desugared_attr_proc(recipients, event, message)
   # Copy the contents of the previous method here and remove this sugar.
   #
   def desugared_interpolation(recipients, event, message)
-    implement_me!
+    mail(message, {
+      :to => recipients.map { |x| x.email },
+      :subject => "You’re invited to " + event.title.to_s + " on " + event.date.to_s})
   end
 
   # Ruby tracks local variables lexically at compile time. Wherever you say `x = y`, the compiler assumes that
@@ -110,7 +120,9 @@ def desugared_interpolation(recipients, event, message)
   # (Think: which names are local variables, and which are not?)
   #
   def desugared_implicit_self(recipients, event, message)
-    implement_me!
+    self.mail(message, {
+      :to => recipients.map { |x| x.email },
+      :subject => "You’re invited to " + event.title.to_s + " on " + event.date.to_s})
   end
 
   # In Ruby, unlike Python, there are no properties distinct from method calls. When you say `x.y`, you are
@@ -131,7 +143,9 @@ def desugared_implicit_self(recipients, event, message)
   # but structurally quite similar!
   #
   def desugared_implicit_parens(recipients, event, message)
-    implement_me!
+    self.mail(message, {
+      :to => recipients.map { |x| x.email() },
+      :subject => "You’re invited to " + event.title().to_s() + " on " + event.date().to_s()})
   end
 
   # In Ruby, every value is an object and every action is a method call. That includes operators. A binary
@@ -153,7 +167,11 @@ def desugared_implicit_parens(recipients, event, message)
   #   get added before the things on the right. (a + b + c) means ((a + b) + c), NOT (a + (b + c)).
   #
   def desugared_operators(recipients, event, message)
-    implement_me!
+    self.mail(message, {
+      :to => recipients.map { |x| x.email() },
+      :subject => "You’re invited to "
+                  .+(event.title().to_s()
+                  .+(" on " + event.date().to_s()))})
   end
 
   # Compare that to the version at the top.

lib/retail_transaction.rb

@@ -39,6 +39,11 @@ def paid?
     state :processing_payment
     state :payment_declined
     state :settled
+    state :refunded
+
+    event :refund do
+      transitions from: :settled, to: :refunded
+    end
 
     event :check_out do
       transitions from: :ringing_up, to: :collecting_payment,

test/retail_transaction_test.rb

@@ -12,6 +12,7 @@
     assert_equal false, tx.processing_payment?
     assert_equal false, tx.settled?
     assert_equal false, tx.payment_declined?
+    assert_equal false, tx.refunded?
   end
 
   it "starts out empty" do
@@ -74,6 +75,10 @@
       tx.process_payment!
     end
 
+    it "cannot be refunded" do
+      assert_equal false, tx.may_refund?
+    end
+
     it "cannot add more items" do
       assert_raises do
         tx.add_item("roller skates")
@@ -152,5 +157,29 @@
     it "cannot be reopened" do
       assert_invalid_transition { tx.reopen! }
     end
+
+    it "can be refunded" do
+      assert_equal true, tx.may_refund?
+    end
   end
+
+  describe "that is refunded" do
+    before(:each) do
+      tx.add_item("bobcat")
+      tx.check_out!
+      tx.payment_info = "15 cents and a nail"
+      tx.process_payment!
+      tx.payment_authorized!
+      tx.refund!
+    end
+
+    it "cannot be refunded again" do
+      assert_equal false, tx.may_refund?
+    end
+
+    it "cannot be reopened" do
+      assert_equal false, tx.may_reopen?
+    end
+end
+
 end