Description
Ah ok basically it took a lot of reading to realise that you need to render all book formats before you publish them. Well I tend to think of it like git. If it is a simple vc use and you don't have many branches created, then in most cases I tend to write a customized function that groups git add, commit and push altogether.
So if a user wants to publish, why do we want to force them to render first, check all formats and then publish. Those who care about format will do it anyways. It is a bit like Microsoft word forcing you to go through all spelling checks before you can save a document if that makes sense.
Same thoughts come in mind with your git example: I would not promote to do git add, git commit, git push because I find it prone to error. However, I see your point.
If such function would be more verbose by default when used interactively in the IDE, would that be useful to you ?
It would mean not changing the current default in the function, but if the function is used interactively, it would ask what you want to do with some confirmation. A bit like usethis interactivity in a way if you know it. It would allow to present to the user a set of option without needing to really know them before hand.
Do you think such thing would answer your case ?
Something like
> bookdown::publish_book()
--> Do you want to render before publishing ?
1: All format
2: Only specific
3: Do not render and publish as-is
Selection: Originally posted by @cderv in #999 (comment)