This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-07
Channels
- # admin-announcements (4)
- # aws (2)
- # beginners (25)
- # boot (116)
- # braid-chat (4)
- # cider (6)
- # cljsjs (4)
- # cljsrn (17)
- # clojure (196)
- # clojure-austin (23)
- # clojure-belgium (5)
- # clojure-dev (78)
- # clojure-dusseldorf (6)
- # clojure-italy (2)
- # clojure-japan (6)
- # clojure-poland (1)
- # clojure-russia (132)
- # clojure-sdn (1)
- # clojure-uk (26)
- # clojurescript (87)
- # code-reviews (3)
- # core-async (26)
- # cursive (8)
- # datomic (40)
- # devcards (8)
- # emacs (4)
- # funcool (32)
- # hoplon (30)
- # jaunt (34)
- # jobs (1)
- # lein-figwheel (1)
- # leiningen (5)
- # om (14)
- # onyx (8)
- # overtone (31)
- # parinfer (14)
- # proton (8)
- # protorepl (1)
- # re-frame (30)
- # reagent (10)
- # spacemacs (2)
- # untangled (107)
- # yada (3)
@jessica: Yeah, I mean that. Just remembered https://github.com/artemyarulin/koh/blob/master/circle.yml. This may be a bit outdated, but may be a starting point how to organise testing. This project has CI integration with CircleCI and runs tests using Node, Phantom and iOS
I guess somebody tried DataScript and then gave up because of performance problems. Can any body tell more about that or DS experience in general?
@artemyarulin: Thanks for the link! I’m trying to replicate my situation with your repo. A couple questions / observations.
1. When trying to require(“react-native”)
from core.cljs, I get the error: Error: Cannot find module 'react-native’
. It’s a bit strange though because the node_modules
is in kohRN
dir, and the src
dir is pretty isolated. Any thoughts there?
2. When I add the cljs-ajax
dependency and require ajax.core
in your project, I hit the same error that I get:
ajax/xml_http_request.cljs:11
(extend-type js/XMLHttpRequest
^
ReferenceError: XMLHttpRequest is not defined
at Object.<anonymous> (<my-dev-directory>/koh/target/tests/ajax/xml_http_request.js:8:1)
3. Seems like other people are having my same issue with requiring react-native (causes SyntaxError: Unexpected token
). Seems like this was added after react-native 0.16.0. (See here for commit: https://github.com/facebook/react-native/commit/f9b744d50137de25357994fe2e829f98104e2242#commitcomment-15405413)
There's so many hurdles to jump through just to get unit tests working. Is everyone hitting the same issue / has anyone found a good way to unit test? Is there a better approach to testing that I should be aware of? I don’t believe it’s a doo
specific issue, but rather a cljs.test
issue, since doo
basically just calls cljs.test/run-tests
.Before now I’ve only used boot-react-native, but I’m trying out re-natal. Running my app on Genymotion for Android, I just see “Waiting for Figwheel to load files” forever. The figwheel repl is connected and I can eval expressions, but nothing prints to the screen even if I click “Reload JS” from the dev menu. Any thoughts?
@adamfrey: Check IP - Use 10.0.2.2 for stock emulator and 10.0.3.2 for genymotion according to http://stackoverflow.com/questions/5806220/how-to-connect-to-my-http-localhost-web-server-from-android-emulator-in-eclips
not sure about re-natal but there might be multiple places which you have to change
@jessica: Yep, like I said it may be outdated a bit Check this issue and a solution https://github.com/drapanjanas/re-natal/issues/32#issuecomment-202098482
you may try to upgrade re-natal to resolve it
2 and 3 related to 1 - if no RN get loaded, then no XmlHTTPRequest wrappers availalbe
It’s rendering now. It looks like I had a cljs runtime error, and I was seeing nothing?
There was no red screen or compilation warning, but then I removed some lines of cljs and it renders fine
could be - usual way to solve it is lein clean && lein cljsbuild once
to make sure there are no syntax errors or whatever
I guess it kinda hangs if you have syntax error and nothing can be compiled - it just waits forever
lein clean
is my least favorite thing about leiningen. I use boot 99% of the time and I’m amazed that people put up with weird errors related to uncleaned assets
I was trying to say that if nothing works - try to check that it actually could be compiled I guess @misha was reporting to #C050HE28Y channel quite the same issue with the same solution