docs: Improve min_st_separators() documentation#1264
Conversation
Current Aviator status
This PR was merged using Aviator.
See the real-time status of this PR on the
Aviator webapp.
Use the Aviator Chrome Extension
to see the status of your PR within GitHub.
|
|
Good question! We can't have maths in example but a workaround would be to create an arbitrary section using R Markdown support. The code in the code chunk is evaluated every time the
https://roxygen2.r-lib.org/articles/rd-formatting.html#code-chunks Note that the section name is currently really bad. 😁 |
|
Thank you! |
min_st_separators() documentation
|
In the tests, we have @maelle: Can you help please? |
|
Probably not the best solution as this is an unexported function 🤪 (so especially confusing for users) I need to make it work to put the call in a separate chunk (using the |
|
Let's just add the comments as an actual code comment, problem solved. Agreed? I would rather not add distracting code to an example which is making an important point about how a function behaves. |
|
I'll experiment with a knitr hook to modify the output without a comment. I fear the comment is distracting too. |
de5b7d5 to
2b37c19
Compare

@maelle Is this the best way to comment on examples? Can we comment using normal text that includes math instead of writing code comments? If yes, can you push to this branch and demonstrate?