[wip] Integration tests #1
Conversation
| @@ -0,0 +1,8 @@ | |||
| -module('Elm.Native.Utils'). | |||
There was a problem hiding this comment.
Elm.Native.* should not be implemented here, I'm thinking of having a new repo on the elmer-compiler organization that mirror those from elm-lang, for example one repo for core, one for html, etc, and they MUST use the same semantic version than the package from elm. So for example, Elm.Native.Utils should be on elmer-core etc. IIRC the elm-compiler just concatenates those Native javascript modules when everything is compiled to javascript. But we must require the user to list each elmer-* native package as another erlang dependency at runtime.
| @@ -60,6 +60,10 @@ dump(erlsrc, Filename, Erl) -> | |||
| Bin = erlang:iolist_to_binary(Src), | |||
| {Filename, Bin}; | |||
|
|
|||
| dump(binary, Filename, Erl) -> | |||
There was a problem hiding this comment.
I think this is the only thing that should be merged then. Perhaps changing the atom to beam could be more explicit.
I'll fix the test to only verify that a compiled beam can be loaded and executed from erlang.
There was a problem hiding this comment.
Actually, the original idea was to have a dump({beam, OutputDirectory}, Filename, Erl) function, that's what would get called by the rebar3_elmer plugin
davoclavo
force-pushed
the
integration_tests
branch
from
ec3d6d3
to
8e5f7b3
Compare
No description provided.