-
Notifications
You must be signed in to change notification settings - Fork 13
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
Avoid need for elmi-to-json on path #11
Comments
A third option is to write a .elmi parser in Rust ^^. |
I have spent some time trying to get the elmi-to-json code compiled into a static library. Is a really pain and I think would be a quite big burden to maintain even if I did get it working. Maybe I need to look into 2. or 3. and see if they are feasible. |
Annoying indeed! In short, what are the main difficulties you encountered? |
Current progress for dropping elmi-to-json altogether rtfeldman/node-test-runner#442 |
Merged #15 |
Currently, we require an elmi-to-json executable to be installed. We would like elm-test-rs to be a stand alone executable and so we need to find an alternative. I see two:
Use Haskell c ffi bindings: http://wiki.haskell.org/FFI_complete_examples#When_main_is_in_C.2B.2B
Go for my way of finding tests. Rough idea goes something like: https://gist.github.com/harrysarson/08acee2e8d8ffb0185b4b1020c08d756
write a .elmi parser in Rust ^^.
I like 2. more but I haven't succiently written down what 2. involves let alone implemeneted it so 1. may be a better short term solution.
The text was updated successfully, but these errors were encountered: