Closed y1yang0 closed 1 week ago
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 83.58%. Comparing base (
45c1afe
) to head (3d0abca
). Report is 1 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
@123liuziming Please take a look at this, it allows both myconf.json and default.json to coexist when user specifies -rule=myconf.json.
What is the expected behaviour if both default rule and custom rule enhance the same method?
What is the expected behaviour if both default rule and custom rule enhance the same method?
Both of them are applied to the same method, regardless of whether they are located in a single JSON file or in two separate files
LGTM, I will try the extension demo in this branch and merge the PR after that.
LGTM, I will try the extension demo in this branch and merge the PR after that.
One unrelated topic: I think we should at least add a test for these demos to ensure they all compile successfully, otherwise they are very fragile and prone to breaking.
LGTM, I will try the extension demo in this branch and merge the PR after that.
One unrelated topic: I think we should at least add a test for these demos to ensure they all compile successfully, otherwise they are very fragile and prone to breaking.
I will add a CI for this
LGTM, I will try the extension demo in this branch and merge the PR after that.
One unrelated topic: I think we should at least add a test for these demos to ensure they all compile successfully, otherwise they are very fragile and prone to breaking.
I will add a CI for this
Thanks for bearing with me!
LGTM
related to #184
RuleJsonFiles is the name of the rule file. It is used to tell instrument tool where to find the instrument rules. Multiple rules are separated by comma. e.g. -rule=rule1.json,rule2.json. By default, new rules are appended to default rules, i.e. -rule=rule1.json,rule2.json is exactly equivalent to -rule=default.json,rule1.json,rule2.json. But if you do want to replace the default rules, you can add a "+" prefix to the rule file name, e.g. -rule=+rule1.json,rule2.json. In this case, the default rules will be replaced by rule1.json, and then rule2.json will be appended to the rules.