Get links to GitHub repos from CRAN information You don’t indicate such links in DESCRIPTION of your package yet, you In this exploration we shall concentrate on CRAN packages that indicateĪ GitHub repo link under the URL field of DESCRIPTION. Gain insights from many, many READMEs! 🔗 README with badges, and is exported, it’d be too bad not to use it to Now since, codemetar::extract_badges exports a nice ame for any
Project Status: Active – The project has reached a stable, usable state and is being actively developed. Library ( "magrittr" ) codemetar :: extract_badges ( "" ) %>% knitr :: kable () text Here is codemetar::extract_badges in action on the Note that the CRAN version of codemetar already featuresĮxtract_badges, but with a badges table creation based on regularĮxpressions only (and a small encoding bug). The badges extraction is based on (in theĬonversion to XML using commonmark (see my recent techĮxtraction and parsing on the first HTML table there is if there’sĪny, which is necessary for badges in table, which we’ve been The README text, we extract and memoize 2 all badges at once to aĭata.frame that we then query. The list might get longer, so instead of using regular expressions on To the README of onboarded packages thanks to work by Karthik
#Tv app repo there was a problem parsing the package software
“review”, information about review of the software if there was one.Ĭodemetar recognizes information from the peer-review badge we add
“contIntegration”, URLs to continuous integration services such as 🔗ĬodeMeta recognized terms include information we’ve been getting from Of codemetar::extract_badges function to explore the diversity ofīadges worn by the READMEs of CRAN packages.
Integration 1 badges in the README! In this note, we’ll take advantage Information collector and parser for the CodeMetaĭigest metadata about an R package in order to fill the termsĮxtracting information from DESCRIPTION but also from e.g. continuous
0 kommentar(er)
