-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement tag based documentation #908
Changes from all commits
f6f93b8
df91e82
7c77e24
5d9d0a6
601667d
47094ca
36b1aba
c03083c
8ddc458
ce5e068
2373694
2741e2c
cdc106f
20b4370
450fd42
efe5359
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -79,6 +79,12 @@ function calls. (#850, #851, @renkun-ken) | |
* Debugging functions (`browser()`, `debug()`, `debugcall()`, `debugonce()`, `trace()`, `undebug()`, `untrace()`) are now part of the default set of undesirable functions to help prevent them from being committed by mistake. (#876, @michaelchirico) | ||
* New linter `package_hooks_linter()` runs a series of checks also done by `R CMD check` on the `.onLoad()`, `.onAttach()`, `.Last.lib()` and `.onDetach()` hooks (#882, @MichaelChirico) | ||
* Improved location information for R parse errors (#894, #892, @renkun-ken and @AshesITR) | ||
* New tag based documentation pages for linters (#888, @AshesITR) | ||
* Each linter has its own help page | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. nit: maybe add an example ", e.g. ?seq_linter" |
||
* `?linters` also links to tag help pages, collecting linters with a similar goal | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. idea (you may have mentioned this/similar before): it may be nice to have an API to set linters by tag in .lintr, WDYT? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. An idea might be to export alll those linter lists like e.g. make something like |
||
* Each linter can have multiple tags | ||
* New function `available_linters()` to list available linters and their tags | ||
This feature is extensible by package authors providing add-on linters for {lintr}. | ||
Comment on lines
+82
to
+87
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Alternatively, we could add the bullets on the top level and duplicate the issue number? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this bullet is pretty vague maybe a See ?available_linters reference? |
||
|
||
# lintr 2.0.1 | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it would help to motivate this (why as lintr user do I care about this update?). maybe a quick blurb like
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Refining:
WDYT