-
Notifications
You must be signed in to change notification settings - Fork 10
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
Revise Ortac/Dune to minimize yet again boilerplate #218
Conversation
This PR is based on #214, please consider only the last 5 commits. |
a8959a8
to
a1fe1cd
Compare
1f8bc90
to
aed44fd
Compare
aed44fd
to
506e072
Compare
506e072
to
fa155d3
Compare
fa155d3
to
419e4ca
Compare
419e4ca
to
2027e09
Compare
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.
This is really nice simplification, thank you! Now I wonder if those default names should not be adopted directly in Ortac/QCheck-STM.
- 8198b4a Remove generation of dune rule generation
I find the phrasing of the commit message unclear, isn’t a negation missing?
Suggestion: “as we want...” → “Future commits will simplify calling out directly thedune qcheck-stm
” from the command line.” (even if I’m not a big fan a talking about future commits in messages, here that might be the needed context) - 9990674 Make config and test name optional
Change the commit title to names, to make it clearer the config is not optional, just its name?
I wondered whether it would be worth having tests for the case the options are actually working when explicitly set, for instance by using them in the examples to preserve the file names used before the PR?
4665003
to
5a54e3e
Compare
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.
A small comment now that I see how ~absent
is rendered.
plugins/dune-rules/README.md
Outdated
This stanza assumes that you have written the configuration for | ||
[Ortac/QCheck-STM] in a file named `lib_config.ml` and that the `Lib` module is | ||
part of the `lib` library. It will write the generated tests in `lib_tests.ml`. | ||
If you want more control, you can use the `--config` `--library` and `--output` |
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.
If you want more control, you can use the `--config` `--library` and `--output` | |
If you want more control, you can use the `--config`, `--library` and `--output` |
This comma sliped in the revision, I think :-)
plugins/dune-rules/src/dune_rules.ml
Outdated
"Concatenation of INTERFACE without the extension and \ | ||
\"_config.ml\"." |
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.
Given how the ~absent
field is rendered, I think I would prefer no initial capital and no ending period.
"Concatenation of INTERFACE without the extension and \ | |
\"_config.ml\"." | |
"concatenation of INTERFACE without the extension and \ | |
\"_config.ml\"" |
5a54e3e
to
bd20450
Compare
The generated dune rules no longer generate the rule to generate themselves. Future commits will simplify calling out directly the dune qcheck-stm.
When the argument is missing, Ortac/Dune will assume that the library has the same name as the module.
The normalisation concerns only the dune and the qcheck-stm plugins for now.
bd20450
to
88f8636
Compare
This PR proposes to:
_config
_tests
].ml
In the best case scenario, this allows to just write: