getOption, hoping I can make some progress today with other callbacks.
pinRemove()and also the auto-generated function references.
BundleRetentionLimit, see https://docs.rstudio.com/connect/1.5.4/admin/appendix-configuration.html
pin()to avoid versioning. I can also implmenet this as a feature request in the comming days (hopefully), the idea would be to support registering RSC board with
versions = FALSEwhich would do behinnd the scenes a delete/re-create operation intead of updating a version. Tracking this work with rstudio/pins#245
Hi @javierluraschi! I’ve been very busy with the new duties lately. Thanks again for the opportunity!
We investigated options for site & docs generation. There are a couple of candidates. But before we propose a solution, could you clarify what do you mean by “live-examples”? Do you mean inline playgrounds where you can change code and see how it works?
Hi @javierluraschi! We tried many existing documentation solutions. And I think that Docusaurus is the most powerful out of all of them and suits the best for our needs.
There is also v1, but I think we can go with v2, despite on the fact that it’s still in alpha. In the end it’s just a documentation generator. We can also go with v1, I think it’s also fine.
Some of the features I like about it:
Another accompanying idea we have to automatically generate awesome documentation is to utilize power of documentation.js.
This tool will allow us to generate Markdown files out of jsdoc comments in the code. And then these Markdown files can be consumed by Docusaurus to create nice-looking pages with library API reference.
If you give us a green light, we can proceed with the setup of the docs site for
board_pin_versions, see for instance: https://github.com/rstudio/pins/blob/abc367be52c3311d15f011e73a6624507dfb42e8/R/board_local.R#L78-L80