You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, thanks for publishing these rules. They're some of the first third-party Bazel rules I've come across that worked out of the box.
I wanted to make you aware of a project I'm working on (bazel-runfiles-server) that adds livereload support to arbitrary Starlark rules, including the Pandoc ones. It allows users to run a single target with ibazel, edit a source file (e.g. Markdown), and have the rerendered output automatically refreshed in the browser. My repo has a working Pandoc example here.
I think it's too early to integrate this directly into your repo (see ongoing conversation with ibazel maintainers here), but I wanted to reach out in case you had feedback about the API, or even really if this workflow is useful to you or your users.
Feel free to close this (it's more of an FYI than an issue).
The text was updated successfully, but these errors were encountered:
That's awesome. Thanks for working on this! I'm going to leave this issue open for a bit, as a reminder that I (and others) should keep an eye on that project.
I'm glad to hear these rules work well for you. I also happen to be the author of rules_elm. Maybe I should try using that in combination with bazel-runfiles-server as well...
First, thanks for publishing these rules. They're some of the first third-party Bazel rules I've come across that worked out of the box.
I wanted to make you aware of a project I'm working on (bazel-runfiles-server) that adds livereload support to arbitrary Starlark rules, including the Pandoc ones. It allows users to run a single target with ibazel, edit a source file (e.g. Markdown), and have the rerendered output automatically refreshed in the browser. My repo has a working Pandoc example here.
I think it's too early to integrate this directly into your repo (see ongoing conversation with ibazel maintainers here), but I wanted to reach out in case you had feedback about the API, or even really if this workflow is useful to you or your users.
Feel free to close this (it's more of an FYI than an issue).
The text was updated successfully, but these errors were encountered: