You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The roles used in the code, as in "Conceptualization", "Methodology" and so on, should be defined in a single place. Do notice that you hard coded (wrote in a script) the roles in function create_template and in test test-read_template.
There are many ways to do it, but the simples is just using a function:
With some simple webscrapping, you could use testthat to check if the template in the package is identical to the template from the site. Whenever the site adds or removes a role, your CHECK process will show it.
The text was updated successfully, but these errors were encountered:
I added the functon roles_get() advancing the name convention suggested in the following issue. I also added a unit test that scraps CRediT and checks if roles are up-to-date. The test is skipped if rvest is not installed or if the tests are not run in local.
@msperlin
The roles used in the code, as in "Conceptualization", "Methodology" and so on, should be defined in a single place. Do notice that you hard coded (wrote in a script) the roles in function create_template and in test test-read_template.
There are many ways to do it, but the simples is just using a function:
With some simple webscrapping, you could use testthat to check if the template in the package is identical to the template from the site. Whenever the site adds or removes a role, your CHECK process will show it.
The text was updated successfully, but these errors were encountered: