From c8b6a1a4a1be5e5c1f5263b7c64afe059282b074 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Javi=20Mart=C3=ADn?= <javim@elretirao.net>
Date: Mon, 27 May 2019 15:24:20 +0200
Subject: [PATCH] Use the same view code for finished budgets

The differences between the custom code and the code in CONSUL didn't
make much sense anymore: the path can be passed a budget instead of an
ID (so it uses a slug) and there's no reason to hide the link to the
executions for the 2018 budget anymore. Furthermore, removing the
`status: 1` parameter makes the link consistent with the rest of the
application, since it was the only link to budget executions using that
parameter.
---
 app/views/budgets/_finished.html.erb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/app/views/budgets/_finished.html.erb b/app/views/budgets/_finished.html.erb
index 97ad2aa18..f7c17fc58 100644
--- a/app/views/budgets/_finished.html.erb
+++ b/app/views/budgets/_finished.html.erb
@@ -16,10 +16,10 @@
               <div class="small-12 medium-6 column table" data-equalizer-watch>
                 <div id="budget_<%= budget.id %>_results" class="table-cell align-middle">
                   <%= link_to t("budgets.index.see_results"),
-                              budget_results_path(budget.id),
+                              budget_results_path(budget),
                               class: "button" %>
                   <%= link_to t("budgets.index.milestones"),
-                              budget_executions_path(budget.id),
+                              budget_executions_path(budget),
                               class: "button" %>
                 </div>
               </div>