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
There are 3 sets of defaults: defaults, branch-formatter, project-formatter.
None of those can lint clj nses beyond a given project, e.g. reachable through the classpath.
That's generally reasonable (one doesn't want to lint 3rd-party code), but now the new formatting-stack.linters.one-resource-per-ns linter would maximise its usefulness by linting these nses.
Task
Create formatting-stack.classpath-linter, analog to project-formatter
but with a classpath-wide scope
should only lint, not format
should only run formatting-stack.linters.one-resource-per-ns
No much point in a broader linting for 3rd party code
Create a strategy that traverses clj namespaces recursively
project namespaces -> namespaces from our deps -> namespaces from transitive deps -> ...
Context
There are 3 sets of defaults:
defaults
,branch-formatter
,project-formatter
.None of those can lint clj nses beyond a given project, e.g. reachable through the classpath.
That's generally reasonable (one doesn't want to lint 3rd-party code), but now the new
formatting-stack.linters.one-resource-per-ns
linter would maximise its usefulness by linting these nses.Task
formatting-stack.classpath-linter
, analog toproject-formatter
formatting-stack.linters.one-resource-per-ns
Acceptance criteria
One can catch this specific instance:
Additional resources
#112
The text was updated successfully, but these errors were encountered: