-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Return empty when searching issues with no repos #26545
Conversation
Fix `https://github.com/go-gitea/gitea/pull/26545#discussion_r1295734340` --------- Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Co-authored-by: Giteabot <teabot@gitea.io>
Fix `https://github.com/go-gitea/gitea/pull/26545#discussion_r1295734340` --------- Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Co-authored-by: Giteabot <teabot@gitea.io>
Backport #26556 by @wolfogre Fix `https://github.com/go-gitea/gitea/pull/26545#discussion_r1295734340` Co-authored-by: Jason Song <i@wolfogre.com> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
// no repos found, don't let the indexer return all repos | ||
opts.RepoIDs = []int64{0} | ||
} | ||
} |
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.
Curious, what's this {}
syntax? Is this a on-demand closure like in JS?
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's an int64
slice literal with a single value 0
in it.
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.
Not that one, I meant the enclosing {}
between lines 460 and 471.
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.
Found it, it's called Block: https://go.dev/ref/spec#Blocks, same as in JS, https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/block
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.
Ah, my bad! Yep, a block.
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.
Never mind, it is just a trick. I usually do this in a relatively separate piece of code, to avoid polluting a broader scope with local variables, especially when the function body is large.
buildIssueOverview
is so big, it has almost 400 lines and at least 20 local variables.
Explicit blocks also make it clear how to refactor them to multiple functions, but I'm too lazy to refactor it right now 😁
* upstream/main: [skip ci] Updated translations via Crowdin Fix various line-height styles (go-gitea#26553) Return empty when searching issues with no repos (go-gitea#26545) Support rebuilding issue indexer manually (go-gitea#26546) Fix label filter between `all` and `no` (go-gitea#26557) Fix "issueReposQueryPattern does not match query" (go-gitea#26556)
Fix #26512.
Replace and close #26515.
Regression of #26012.
After this: