Not sure if I'm going something wrong, bit watches rarely work for me. As for debugging, there are times when it's just easier to click through your app to the point it breaks and see the function params than manually replicate the app state at that point via REPL. I also find identifying bugs in recursive calls easier in a debugger.
On Sun, Nov 9, 2014, 11:14 AM Aleš Roubíček <[email protected]> wrote: > On Sunday, November 9, 2014 3:21:19 PM UTC+1, Rory Douglas wrote: > > -What do you mean by CLJS debugging via Chrome DevTools ? > > > > > > You can use the Source tab to set breakpoints on the CLJS files (works > thanks to the source maps), and step through your code. A similar tool > for Clojure itself would be awesome :-) > > The need for debugging with InstaRepl and watches is a bit weird for me. > > -- > Note that posts from new members are moderated - please be patient with > your first post. > --- > You received this message because you are subscribed to a topic in the > Google Groups "ClojureScript" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/clojurescript/RKO3YH0dQnk/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/clojurescript. > -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
