feature: add whitelist class #7973
Open
+994
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## 2.x #7973 +/- ##
============================================
+ Coverage 71.74% 71.86% +0.11%
Complexity 872 872
============================================
Files 1300 1302 +2
Lines 49727 49901 +174
Branches 5908 5929 +21
============================================
+ Hits 35678 35859 +181
+ Misses 11114 11099 -15
- Partials 2935 2943 +8
... and 9 files with indirect coverage changes 🚀 New features to boost your workflow:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ⅰ. Describe what this PR did
添加了 JSON 白名单安全机制
Added JSON whitelist security mechanism
白名单使用方法：
配置方式
application.yml:
application.properties:
seata.json.allowlist=com.company.model.,com.company.dto.,com.company.UserPo配置规则
xxx.com.company.model.xxxcom.company.UserPoConfiguration Method
application.yml:
application.properties:
seata.json.allowlist=com.company.model.,com.company.dto.,com.company.UserPoConfiguration Rules
xxx.com.company.model.xxxcom.company.UserPoⅡ. Does this pull request fix one issue?
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews