-
Notifications
You must be signed in to change notification settings - Fork 94
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
Creates a dedicated rule to generate support files #1000
Conversation
src/html_support_files/dune
Outdated
@@ -2,7 +2,7 @@ | |||
; of the vendored projects. | |||
|
|||
(rule | |||
(alias runtest) | |||
(alias html-support-files) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can it be both run by both runtest
and html-support-files
(we want the tests in CI to detect an unpromoted html_support_files)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit-picking, but why so long? Since it is something we will actually type...
(alias html-support-files) | |
(alias support-files) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dune's manual suggests using (aliases runtest support-files)
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But how do we know whether the support files are uptodate ? The previous rule was tested in CI for free.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. This will be useful to solve merge conflicts for html support files without having to recompile everything.
Currently, regenerating support files requires using the test rule, which feels weird because changing the css has very little to do with tests. It also allows to generate the support files without running the test more easily.