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
Using ::aliased/keywords rather than fully qualified namespaced keywords can cause developer friction when working with a code base, because such keywords cannot reliably be found / replaced etc with simple tools, e.g. grep.
Suggested solution
Adding a clj-kondo linter (probably :off by default) that could warn when an aliased keyword is used will allow a team to help ensure keyword call sites can more easily be found.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Problem
Using
::aliased/keywords
rather than fully qualified namespaced keywords can cause developer friction when working with a code base, because such keywords cannot reliably be found / replaced etc with simple tools, e.g.grep
.Suggested solution
Adding a clj-kondo linter (probably
:off
by default) that could warn when an aliased keyword is used will allow a team to help ensure keyword call sites can more easily be found.For example this code would generate a warning:
The text was updated successfully, but these errors were encountered: