Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Running on all file saves #5

Closed
devinrhode2 opened this issue Sep 1, 2016 · 3 comments
Closed

Running on all file saves #5

devinrhode2 opened this issue Sep 1, 2016 · 3 comments

Comments

@devinrhode2
Copy link

devinrhode2 commented Sep 1, 2016 •
edited
Loading

It'd be great if elm-doctest was run on all file saves, and that a user got feedback just like a regular elm compiler error. Don't know if it'd be better to tie in with elm-reactor or latch onto/plug into elm, but I think getting errors inline in one's editor would be the slickest.
@tshm
Copy link
Owner

tshm commented Sep 2, 2016

I guess one can use a file-watcher script such as fsmonitor and such.
I think we should let user to choose whatever the tool that they want to use or already using.
I'll keep this issue open as I'm not sure.

@tshm
Copy link
Owner

tshm commented Nov 3, 2016

release-0.2.0 takes care of watching now.

@tshm tshm closed this as completed Nov 3, 2016
@devinrhode2
Copy link
Author

Yay!

On 3 Nov 2016 07:36, "tosh shimayama" notifications@github.com wrote:

Closed #5 #5.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#5 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAg8qBHwN1lugG1S8fwqKk94Y2YQfdGSks5q6fFOgaJpZM4JyPb3
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tshm @devinrhode2