-
Notifications
You must be signed in to change notification settings - Fork 79
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
Tracking issue: trigger rerun on non-.rs-file changes #31
Comments
Less edge-casey example: the |
If rust-lang/cargo#1989 is implemented then that could take care of determining what files are important. |
For my reference, the linked issue actually asks for a Cargo API that gives the list of paths that would trigger a recompile. |
👍 Going to do this. Don't have an ETA, but it's on the todolist. |
Being able to watch .md files would also be really useful for automatically generating the docs. |
This is now done with the entirely new version 4.0.0! |
Changes of files, whose names do not end with
.rs
are currently ignored. Sometimes other files are expected to trigger a rerun of compilation. Two examples:lalrpop
will generate.rs
files from.lalrpop
files that are in the source directoryinclude_str!
or something similarThe text was updated successfully, but these errors were encountered: