reprazent / mealz Goto Github PK

So users can pick several names that will link to this user

Meals should become canceled:

• Save a canceled_at date
• Recalculate the balance for all users
• Delete wrongly created users (if the user has no mealz left after deleting)

m.users.each do |eater|
  eater.balance -= m.amount if eater == m.payed_by
  eater.balance += m.amount / m.users.count
  eater.save!
end

This could go in a new seperate MealDestroyer

Saving when a user was archived.

• When a user is archived it is no longer counted for in the balances
• Adding a meal with an archived user, unarchives him

Do a double bookkeeping system, so keep track of outgoing payments and incoming payments. That way we're always up to date with the balances and calculating them will be a snap.

Things left as an exercise for the reader:

• [] Think of a way to keep track of current balance state
• [] Make code below do actual things

class Mealz
# Van elke user per maaltijd
  has_many :incoming_payments

# Winkel en de user die is gaan halen
  has_many :outgoing_payments

  payment :reason
end

class Payment
      belongs_to :user
      belongs_to :meal

# amount
# reason
# kind
end

# Bob en Piet eten mee
# Bob is eten halen

OutgoingPayment.new(user: bob, 30, reason: "shopping")
IncomingPayment.new(user: piet, 30/2, reason: "eating")
IncomingPayment.new(user: bob, 30/2, reason: "eating")

Creating a meal in advance would allow people to subscribe to it.
So a meal would then have many users trough a request, request can have an extra "requests" property.
Saying something like ik eet mee: oude kaas, stokbrood would create a meal without a payer/amount/... if none exists, or add the request to an already existing meal.

This would need #5 to be done first, so we can cancel a meal if we later on decide not to go.

To run all the tests.

Gewoon getrouwd! Proficiat!