-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
:init.restart() #45
Comments
Related gist which may help you with further ideas: https://gist.github.com/josevalim/a5e747c90a72e40a4b52062ea6919877 |
Gosh. Suddenly all that work seems a bit pointless. :P Thanks for the info! |
I think we still need the watching bit, just the restart bit that got much much easier! :D |
The watching is easy thanks to One of the features I want is having IEx running at the same time so that one can type expressions in the repl while the tests are not running. If we use |
Yes :( |
Perhaps we can support both once we get test modules closing after an exception is thrown when compiling them. (keen to take a stab at this myself, but have had a busy week) There are advantages to each method. The |
Yeah, it may be faster with the risk of potentially running on outdated state. |
Yes I think people have had problems with state in Phoenix applications already. I need to find some time to read the rebar3 autotest plugin so I can see how it is managed there. It re-uses the VM and features a repl. |
Closing as |
I am not sure this is the best way to let you know but I have just found out there is a command called :init.restart() that will restart the whole system, shutting down all applications and starting them again. For example, if you do:
It will restart everything and run the tests again. Maybe this can be used to make this project much more straight-forward. :)
The text was updated successfully, but these errors were encountered: