summaryrefslogtreecommitdiff
path: root/billing/app/views/customers
diff options
context:
space:
mode:
authorjessib <jessib@leap.se>2013-05-07 14:15:17 -0700
committerAzul <azul@leap.se>2013-07-17 10:47:13 +0200
commit41eb0f61e46731fda2381369a2a307eca32ea7f3 (patch)
tree6605486a9a73847135e02dbb76bd659e56aed025 /billing/app/views/customers
parenta00470d0c046774edc94ef01ef9bc590e8d58ac9 (diff)
Note about knowing sort order for returned transactions
Diffstat (limited to 'billing/app/views/customers')
-rw-r--r--billing/app/views/customers/show.html.haml2
1 files changed, 1 insertions, 1 deletions
diff --git a/billing/app/views/customers/show.html.haml b/billing/app/views/customers/show.html.haml
index 1e4c5ae..d385d98 100644
--- a/billing/app/views/customers/show.html.haml
+++ b/billing/app/views/customers/show.html.haml
@@ -2,7 +2,7 @@
= link_to 'Make Payment', new_payment_path, :class => :btn
%h3 Last three transactions
- counter = 0
-= # asked http://stackoverflow.com/questions/16425475/order-of-transactions-returned-by-braintree-api to confirm order will always be most recent first
+= # these will be ordered with most recently created first, per http://stackoverflow.com/questions/16425475/
- @braintree_data.transactions.each do |t|
- break if counter > 2 # not ruby-like, but object is a Braintree::ResourceCollection so limited methods available
= render :partial => "payments/transaction_details", :locals => {:transaction => t}