@daviwil thanks man

guys when i define a route with secretary within reagent app, when reload the page i got page not found why?

is your backend is serving your js and executing it for that route?

Hey all, I have seen this pattern, only once, but I wanted to get opinions on it: Example 1

(defn form-3-component
  [props]
  (let [state (atom {:list [] :contacts []})
         on-click! (fn [] (reset! @atom []))]))  <--- take note of this

(defn delete-list-items 
  [list-state]
  (reset! @list-state []))

(defn form-3-component
  [props]
  (let [state (atom {:list [] :contacts []})
         on-click! delete-list-items]   <--- extracted the function from example 1 and brought it outside the component
    ;; lots of stuff happening
    (on-click! (:list @state))))

I was a bit confused at first. I think that's a form-2, not a form-3 component

and I think that's mostly fine. you'd actually pass in the whole state atom into delete-list-items, and I would usually bind the on-click! to the state when you create the atom

(defn delete-list-items 
  [state]
  (swap! state assoc :list []))

(defn form-2-component
  [props]
  (let [state (atom {:list [] :contacts []})
         on-click! #(delete-list-items state)]
    ;; ...
    [:button {:on-click on-click!} "Delete list"]))

I don't think you should deref the atom in reset!... also the arity is wrong, I belive

Maybe you want (swap! state assoc :list [])