Commit f5e0fd2
authored
Sharing one of my favorite "scopes" in intellij, and making it easier to add more (#1182)
Goland is nice, and the type-based navigation is wildly superior to gopls-driven
stuff in my experience, so I tend to lean hard on it when I'm able.
By default though, Goland searches *everything*. All the time.
That's totally reasonable as a default, but we can do better:
- Tests are not usually all that interesting when trying to understand and navigate code.
(perhaps they should be, but that's more a platonic ideal than a reality)
- Generated RPC code is almost never useful to dive into. The exposed API surface is sufficient,
if it compiles, it's correct.
- Non-Go files are just less interesting in a Go project.
So this scope excludes ^ all that.
To add more shared ones, just check the "share through vcs" box and commit it.
To use it, just select the scope from the dropdown when you search. E.g. "find in files" ->
change from "in project" to "scope" -> change the dropdown. This custom scope will now appear,
and it'll remember what you last used, so it's a nice default.
This also works in "call hierarchy", "go to implementations" (open it in a panel to configure it,
with the gear on the side. it's awful UI but it works), etc quite a lot of places.
This same kinda-obtuse search-scope query language can be used to mark things as generated or test
related, which will also help other parts of the IDE mark things as more or less relevant for you.
It's worth exploring a bit, scopes and filters can be used to do a lot: https://www.jetbrains.com/help/idea/scope-language-syntax-reference.html1 parent 4c1c0de commit f5e0fd2
2 files changed
+10
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
1 | 2 | | |
2 | 3 | | |
3 | 4 | | |
4 | 5 | | |
5 | | - | |
6 | 6 | | |
7 | 7 | | |
8 | 8 | | |
| |||
17 | 17 | | |
18 | 18 | | |
19 | 19 | | |
| 20 | + | |
| 21 | + | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
0 commit comments