gitea/modules/indexer/issues
Nanguan Lin 1eae2aadae
Fix issue not showing on default board and add test (#27720)
See https://github.com/go-gitea/gitea/pull/27718#issuecomment-1773743014
. Add a test to ensure its behavior.
Why this test uses `ProjectBoardID=0`? Because in `SearchOptions`,
`ProjectBoardID=0` means what it is. But in `IssueOptions`,
`ProjectBoardID=0` means there is no condition, and
`ProjectBoardID=db.NoConditionID` means the board ID = 0.
It's really confusing. Probably it's better to separate the db search
engine and the other issue search code. It's really two different
systems. As far as I can see, `IssueOptions` is not necessary for most
of the code, which has very simple issue search conditions.
2023-10-25 11:51:49 +00:00
..
bleve Refactor and enhance issue indexer to support both searching, filtering and paging (#26012) 2023-07-31 06:28:53 +00:00
db Clean some functions about project issue (#27705) 2023-10-20 14:01:25 +02:00
elasticsearch Refactor and enhance issue indexer to support both searching, filtering and paging (#26012) 2023-07-31 06:28:53 +00:00
internal Replace util.SliceXxx with slices.Xxx (#26958) 2023-09-07 09:37:47 +00:00
meilisearch Refactor and enhance issue indexer to support both searching, filtering and paging (#26012) 2023-07-31 06:28:53 +00:00
dboptions.go Explain SearchOptions and fix ToSearchOptions (#26542) 2023-08-16 15:40:13 +00:00
indexer_test.go Fix issue not showing on default board and add test (#27720) 2023-10-25 11:51:49 +00:00
indexer.go Improve retrying index issues (#27554) 2023-10-15 18:56:57 +00:00
util.go Improve retrying index issues (#27554) 2023-10-15 18:56:57 +00:00