From 031a777c8c8c84163c9a00f8386847d7e977a802 Mon Sep 17 00:00:00 2001 From: dimovich Date: Sun, 8 Sep 2019 18:28:50 +0300 Subject: [PATCH] Fix event definitions for routes with parameters The current implementation will fail for `(re-frame/dispatch [::navigate ::some-route {:some :params}])`. Update the definitions of `::navigate` and `::navigated!` events to accept the full route arguments. --- .../frontend-re-frame/src/cljs/frontend_re_frame/core.cljs | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/examples/frontend-re-frame/src/cljs/frontend_re_frame/core.cljs b/examples/frontend-re-frame/src/cljs/frontend_re_frame/core.cljs index f7b33cc8..a15a34b0 100644 --- a/examples/frontend-re-frame/src/cljs/frontend_re_frame/core.cljs +++ b/examples/frontend-re-frame/src/cljs/frontend_re_frame/core.cljs @@ -18,7 +18,7 @@ (re-frame/reg-event-fx ::navigate - (fn [db [_ route]] + (fn [db [_ & route]] ;; See `navigate` effect in routes.cljs {::navigate! route})) @@ -59,8 +59,8 @@ ;; Triggering navigation from events. (re-frame/reg-fx ::navigate! - (fn [k params query] - (rfe/push-state k params query))) + (fn [route] + (apply rfe/push-state route))) ;;; Routes ;;;