-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ClojureScript support #51
Conversation
This reverts commit 137fb09.
…pile of user projects
…tations.cljs namespace) or bad things happen: undeclared vars warnings and tests do not run
Awesome! |
I'd like to help maintain the project. |
Can you take a look at getting the failure examples failing again? It On Monday, February 23, 2015, Ivan Mikushin notifications@github.com
Any fool can write a test that helps them today. Good programmers write |
Sure. I'll take a look. On Tue, Feb 24, 2015, 17:01 jaycfields notifications@github.com wrote:
|
I've just diffed the two |
I agree, looks good to me too. On Tue, Feb 24, 2015 at 9:41 AM, Ivan Mikushin notifications@github.com
Any fool can write a test that helps them today. Good programmers write |
May I ask what the status on this is? I see Trying with `[org.clojure/clojurescript "0.0-3126"]``. Have an experimental skeleton test ns for this repo.: Calling
So the run is choking on
So it looks like Any idea if I'm doing something obviously wrong (config maybe?), or is the Cljs support not quite ready yet? Thanks a lot for any info! Cheers :-) |
Peter, I'm taking a look. Will definitely follow up on this. |
Thanks Ivan, much appreciated! Just let me know if you can use any other info. |
@ptaoussanis this is a bug introduced in a newer ClojureScript release. I'll try to triangulate and hack a workaround. |
[org.clojure/clojurescript "0.0-2985"] is the last release without this bug |
Oh, interesting. I've been having fun with ClojureScript today myself. Thanks for looking into this. No urgency btw, please take your time. |
Please take a look: taoensso/encore#12 |
Since 0.0-2985 ClojureScript introduced macro symbols in its analysis map and expectation used them to construct vars for test defs, hence the failure described here: clojure-expectations#51 (comment)
@jaycfields @ptaoussanis I've finally found some time to take a close look at the issue. Please, take a look at PR #55 |
merged. thx Ivan |
Thank you! Much appreciated :-) |
You're welcome! :) |
done. Sorry, missed that step. On Thu, Apr 16, 2015 at 8:05 AM, Ivan Mikushin notifications@github.com
Any fool can write a test that helps them today. Good programmers write |
Wow, that was fast!! |
No worries, thx for the updates. :) On Thu, Apr 16, 2015 at 8:08 AM, Ivan Mikushin notifications@github.com
Any fool can write a test that helps them today. Good programmers write |
Support for ClojureScript made possible by CLJX and adrenaline. Fixes #11.
Clojure code had to be refactored a bit to become more cross-plaform, macro-generated var naming had to be fixed (get rid of
gensym
) as well as compile time var user metadata support in ClojureScript upstream. The result: we can now use Expectations from ClojureScript: