forked from mirror/gitea
1eae2aadae
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. |
||
|---|---|---|
| .. | ||
| assignees_test.go | ||
| assignees.go | ||
| comment_code.go | ||
| comment_list.go | ||
| comment_test.go | ||
| comment.go | ||
| content_history_test.go | ||
| content_history.go | ||
| dependency_test.go | ||
| dependency.go | ||
| issue_index.go | ||
| issue_label_test.go | ||
| issue_label.go | ||
| issue_list_test.go | ||
| issue_list.go | ||
| issue_lock.go | ||
| issue_project.go | ||
| issue_search.go | ||
| issue_stats.go | ||
| issue_test.go | ||
| issue_update.go | ||
| issue_user_test.go | ||
| issue_user.go | ||
| issue_watch_test.go | ||
| issue_watch.go | ||
| issue_xref_test.go | ||
| issue_xref.go | ||
| issue.go | ||
| label_test.go | ||
| label.go | ||
| main_test.go | ||
| milestone_list.go | ||
| milestone_test.go | ||
| milestone.go | ||
| pull_list.go | ||
| pull_test.go | ||
| pull.go | ||
| reaction_test.go | ||
| reaction.go | ||
| review_list.go | ||
| review_test.go | ||
| review.go | ||
| stopwatch_test.go | ||
| stopwatch.go | ||
| tracked_time_test.go | ||
| tracked_time.go | ||