Skip to content
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

feat: 规则审计-策略新增/编辑-后端接口 --story=121513458 #526

Merged

Conversation

0RAJA
Copy link
Collaborator

@0RAJA 0RAJA commented Jan 13, 2025

【优化】

  1. 优化联表列表接口
  2. 优化异常信息

【优化】
1. 优化联表列表接口
2. 优化异常信息
@0RAJA 0RAJA merged commit 2c90173 into TencentBlueKing:feat_rule_audit Jan 13, 2025
5 checks passed
@0RAJA 0RAJA deleted the feat_rule_audit_strategy branch January 13, 2025 05:49
@codecov-commenter
Copy link

Codecov Report

Attention: Patch coverage is 33.33333% with 4 lines in your changes missing coverage. Please review.

Project coverage is 62.93%. Comparing base (90bb1ee) to head (f8f0bb0).
Report is 4 commits behind head on feat_rule_audit.

Files with missing lines Patch % Lines
src/backend/services/web/analyze/exceptions.py 50.00% 2 Missing ⚠️
...ackend/services/web/analyze/controls/rule_audit.py 0.00% 1 Missing ⚠️
src/backend/services/web/strategy_v2/resources.py 0.00% 1 Missing ⚠️
Additional details and impacted files
@@                 Coverage Diff                 @@
##           feat_rule_audit     #526      +/-   ##
===================================================
- Coverage            62.94%   62.93%   -0.01%     
===================================================
  Files                  534      534              
  Lines                18013    18016       +3     
===================================================
+ Hits                 11338    11339       +1     
- Misses                6675     6677       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants