dfe-analytical-services / dfe-analytical-services/eesyapi.R

Work out how to set custom lintr parameters in package structure

Open
#18 0 comments 0 reactions 0 assignees View on GitHub
bug help wanted
Dominant language
R
Stars
3
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Currently we have a note flagging that the .lintr file shouldn't exist, we're using this as the config to set custom lintr parameters.

![image](https://github.com/user-attachments/assets/29e0aa56-05a2-4da0-a080-bcd416381869)

CRAN guidance suggests this kind of file shouldn't be in the root of the package so we'll need to find an alternative way (or bite the bullet and be strict on the 80 character limit for all lines) - https://cran.r-project.org/doc/manuals/R-exts.html#Package-structure-1

Contributor guide

Open the contributing guide

Research direction

Inspect the root .lintr file and read the linked CRAN Package structure guidance first. Determine where custom lintr parameters can live without violating CRAN guidance; done means the package retains its intended lint configuration without the prohibited root file, or adopts the documented 80-character rule.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
build-system, tooling
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.