-
Notifications
You must be signed in to change notification settings - Fork 95
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
Revert to outputing a content-empty file when rendering a hidden module #1069
Conversation
Hidden modules were not rendered, since calling html-generate on them was used to generate the associated source code. However, this breaks dune rules in some cases (see issue ocaml#1013), as dune always expect an output to the command. This fix puts back the old behaviour with regard to rendering hidden files. It is related to the separation of implementation and interface pipelines (see Signed-off-by: Paul-Elliot <[email protected]>
Signed-off-by: Paul-Elliot <[email protected]>
Signed-off-by: Paul-Elliot <[email protected]>
It seems to be working - thanks!
|
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.
Looks good!
What do you think of deprecating this behavior so it can be removed again later ?
I'm not sure it's necessary. We'll certainly need a fix to dune for this issue - even with this PR merged dune will produce a completely empty file for modules with double underscores, which is of no use to anyone. Once that's fixed (and we've merged the PR changing how we do source rendering), nobody will ever be calling |
I agree that having |
Signed-off-by: Paul-Elliot <[email protected]>
I agree, it make sense to always generate something and the driver can easily skip generating these. The new paragraph is a nice touch ! |
Signed-off-by: Paul-Elliot <[email protected]>
Hidden modules stopped creating an output file with "render source code", since calling
html-generate
on them was used to generate the associated source code.However, this breaks dune rules in some cases (see issue #1013), as dune always expect an output to the execution of the command. See #1013 for a case where it happens.
With the separation of implementation and interface pipelines (see #1067), we will stop generating those content-empty files when rendering source code.
I think this fix should be included as a hotfix to the
2.3
and2.4
branches, to maintain compatibility with dune rules (and ensureeio
can build its doc).@talex5 could you confirm that this patch fixes your issue?