@statnmap

360 Followers
44 Following
130 Posts
A new blog post on my website: "Spatial correlation between rasters using 'terra'"
πŸ‘ An updated version of a two years old blog post of mine
πŸ‘‰ https://statnmap.com/2024-12-06-spatial-correlation-between-rasters-using-terra/
#rstats #rspatial
Creating a Node.js Website with GitHub Copilot Workspace Using Best Development Practices in R

As a developer primarily focused on R, I strive to follow good development practices: writing clear user documentation with articles and examples; creating robust tests; and automating checks and deployments with CI/CD workflows. These habits have allowed me to build reliable and maintainable projects, but I asked myself: Are these practices transferable if I venture into a different ecosystem, such as Node.js? To answer this question, I set myself a personal challenge: create a fully functional website using Node.js and JavaScript, while taking the opportunity to test GitHub Copilot Workspace as my primary development assistant. My goal was to see if Copilot could guide me from start to finish, assuming I knew nothing. I also wanted to test the hypothesis that even without deep expertise in a language or framework, success is achievable by relying on solid practices and the right tools.

StatnMap

All new features and changes of version 0.6.0 are listed in the news:

πŸ”—https://thinkr-open.github.io/fusen/news/index.html#fusen-060

#Rstats

Changelog

#RStats - Which functions of my package are exported πŸ‘€ or not πŸ™ˆ and where are they located ?
πŸ’ͺ Find it out with fusen::draw_package_structure() - Works for regular packages or 'fusen' built packages
πŸ‘‰ https://thinkr-open.github.io/fusen/articles/draw-a-tree-of-your-package-files-and-functions.html
πŸŽ‰ fusen-v0.6.0 is now on CRAN
Draw a tree of your package files and functions

fusen

#Rstats - A new version of #fusen v0.5.2 is on its way to CRAN πŸŽ‰

πŸ’ͺ The 'inflate_all()' functions now allow to run your prefered code styler between inflate and check.
πŸ‘‰ doc: https://thinkr-open.github.io/fusen/articles/inflate-all-your-flat-files.html#complete-the-process-with-your-own-code-style

For instance:

fusen::inflate_all_no_check(stylers = function() {
styler::style_pkg()
styler::style_dir("dev")
})

Inflate all your flat files

fusen

πŸŽ‰ New version of #fusen is on #CRAN πŸŽ‰ There are some huge modifications !
πŸ—’οΈ Read the following vignettes to know more
πŸ’¨ inflate all flat files at once: https://thinkr-open.github.io/fusen/articles/inflate-all-your-flat-files.html
πŸ™ init the project on #github with full HTML documentation ready: https://thinkr-open.github.io/fusen/articles/share-on-a-github-website.html
πŸ“” List created files in a config file: https://thinkr-open.github.io/fusen/articles/register-files-in-config.html
Inflate all your flat files

fusen

πŸ“’PDF of my prez: "#golem and #fusen: The winning combo for building robust, easy-to-manage #shiny applications" for @rencontres_R Avignon

πŸ’ͺ Separate UI from business dev. Build a developers documentation.
πŸ”—https://github.com/statnmap/prez/blob/master/2023-06-22_RR2023_golem-fusen.pdf
#RStats #RR2023
prez/2023-06-22_RR2023_golem-fusen.pdf at master Β· statnmap/prez

My presentations. Contribute to statnmap/prez development by creating an account on GitHub.

GitHub
New blog post: "How to debug your package in a #rhub fedora container before sending it to CRAN?"
πŸ”— https://statnmap.com/2023-06-20-how-to-debug-your-package-in-a-rhub-fedora-container-before-sending-to-cran/
#RStats
Creating a Node.js Website with GitHub Copilot Workspace Using Best Development Practices in R

As a developer primarily focused on R, I strive to follow good development practices: writing clear user documentation with articles and examples; creating robust tests; and automating checks and deployments with CI/CD workflows. These habits have allowed me to build reliable and maintainable projects, but I asked myself: Are these practices transferable if I venture into a different ecosystem, such as Node.js? To answer this question, I set myself a personal challenge: create a fully functional website using Node.js and JavaScript, while taking the opportunity to test GitHub Copilot Workspace as my primary development assistant. My goal was to see if Copilot could guide me from start to finish, assuming I knew nothing. I also wanted to test the hypothesis that even without deep expertise in a language or framework, success is achievable by relying on solid practices and the right tools.

StatnMap
If you use #fusen to dev your package, use this trick to pre-compile your vignettes:
πŸ‘‰ "inflate()" and then "knit()" the vignette over itself
πŸ’ͺ Keep the source and commands in "dev/flat_file.Rmd", get a properly pre-compiled vignette, clean of manual knit commands
#RStats
Nouveau rdv Γ  Nantes : "C'est quoi {shiny} ? Comment je fais un site web interactif avec R ?"
πŸ’ͺRetour d'expΓ©rience avec Ambre Pioger et Damien Gourret Baumgart
πŸ‘‰ Inscriptions: https://www.meetup.com/fr-FR/meetup-r-nantes/events/291092717/
#Meetup #Nantes
#RStats
Soutenu par le #RConsortium
C'est quoi {shiny} ? Comment je fais un site web interactif avec R ?, mar. 28 fΓ©vr. 2023, 19:00 | Meetup

Pour ce nouveau rendez-vous, nous vous proposons une session en prΓ©sentiel avec **Ambre Pioger** et **Damien Gourret Baumgart**. Nous parlerons {shiny} et {shinymanager}.

Meetup
In dev version 0.5.0 of #fusen, when inflating your flat #RMarkdown file into a #RStats package, it will list all function, test, and vignette files created in a config YAML.
Soon, this will allow to clean obsolete files in case of bad inflate or changing function names.
See the ongoing feature there: https://thinkr-open.github.io/fusen/dev/articles/clean-fusen-files.html
Clean {fusen} files

fusen