-
-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
refactor: using indexes to query post lists #5230
Conversation
cc13f0b
to
7a55860
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #5230 +/- ##
============================================
- Coverage 57.18% 57.08% -0.11%
+ Complexity 3384 3364 -20
============================================
Files 587 585 -2
Lines 19235 19178 -57
Branches 1460 1427 -33
============================================
- Hits 10999 10947 -52
+ Misses 7652 7645 -7
- Partials 584 586 +2 ☔ View full report in Codecov by Sentry. |
4548752
to
d30d300
Compare
d30d300
to
f325985
Compare
TODO:
|
745d663
to
fdb80cf
Compare
fdb80cf
to
07c380a
Compare
Signed-off-by: Ryan Wang <[email protected]>
Signed-off-by: Ryan Wang <[email protected]>
e0ac85b
to
a24792d
Compare
ok to test and ready for review |
/lgtm |
Signed-off-by: Ryan Wang <[email protected]>
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.
/lgtm
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.
/lgtm
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: LIlGG The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
/area core
/area console
/milestone 2.12.x
What this PR does / why we need it:
使用索引功能来查询文章列表
how to test it?
Which issue(s) this PR fixes:
Fixes #5223
Does this PR introduce a user-facing change?