This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-03-21
Channels
- # admin-announcements (4)
- # aleph (1)
- # beginners (15)
- # boot (55)
- # braveandtrue (5)
- # cider (20)
- # clara (10)
- # cljs-dev (13)
- # cljsrn (8)
- # clojure (52)
- # clojure-austin (30)
- # clojure-brasil (2)
- # clojure-india (1)
- # clojure-italy (2)
- # clojure-nl (1)
- # clojure-russia (72)
- # clojure-sdn (9)
- # clojure-taiwan (2)
- # clojure-uk (45)
- # clojurebridge (3)
- # clojured (1)
- # clojurescript (46)
- # core-matrix (1)
- # cryogen (1)
- # cursive (43)
- # datascript (12)
- # datomic (57)
- # devcards (54)
- # emacs (6)
- # funcool (21)
- # hoplon (335)
- # jobs (15)
- # jobs-rus (40)
- # ldnclj (2)
- # lein-figwheel (20)
- # off-topic (59)
- # om (157)
- # onyx (29)
- # parinfer (2)
- # pedestal (26)
- # proton (9)
- # protorepl (2)
- # reagent (3)
- # ring-swagger (4)
- # spacemacs (2)
- # untangled (17)
anyone else run into this error?
JVM_OPTS="-Dtutorial" lein run -m clojure.main script/figwheel.clj
STARTING FIGWHEEL ON BUILDS: (tutorial)
Figwheel: Starting server at
Figwheel: Watching build - tutorial
Compiling "resources/public/js/tutorial.js" from ["src/tutorial" "src/shared"]...
{:tag :cljs/analysis-error}
ANALYSIS ERROR: Could not locate untangled_tutorial/tutmacros__init.class or untangled_tutorial/tutmacros.clj on classpath. Please check that namespaces with dashes use underscores in the Clojure file name. in file src/tutorial/untangled_tutorial/G_Mutation_Exercises.cljs on file null, line null, column null
@zirmite: I did some additions this weekend. I'll try re-running it on my end as well.
yeah, missed something in source paths in project file when I added macros...weird that it didn't fail on my other machine
@polymeris: On SQL, since that is going to come up alot. What @ethangracer said. We're not using it (for anything yet), but we're trying to make it as simple as possible to hook it in. It seems technically possible to convert Om/Pull query syntax into limited kinds of SQL queries (e.g. turn Om joins into SQL joins, treat namespaces as table names, property names as column names, etc). It is a pretty interesting problem. The simpler approach would be to just have some logic at the server query processing level that detects a certain query, runs some hand-written SQL, and the transforms the result back to the proper form for Om. Not elegant, but certainly no worse than what you already do with REST. So, from our perspective Datomic is a really nice match in that it simplifies both sides. If you have to use SQL on the back-end, you still get the front-end benefits.