fix: remote logic rules cannot be parsed

[HolgerHuo]

Logic rules like AND,OR,SUB-RULE, etc have a different rule structure than traditional rules. The parser used in ./config/config.go was updated accordingly when adding these rule types but the parser used in ./rules/provider/parse.go was not, making logic rules in remote providers not working as expected.

[Skyxim]

Are there any specific examples of errors? If you change it like this, it will affect the nested logic rules.

[HolgerHuo]

For example, if we have a remote rule provider like the following:

payload:
  - AND,((IP-CIDR,192.168.1.0/24),(RULE-SET,Microsoft))

[xishang0128]

It is a mistake to introduce complex rules into a rule set, which will lead to difficulty in parsing and various problems.

[HolgerHuo]

It is a mistake to introduce complex rules into a rule set, which will lead to difficulty in parsing and various problems.

As is in my case, I use rule sets for separating routing logics from clash core as we currently have no api for modifying rules from REST api.

If you change it like this, it will affect the nested logic rules.

Did you mean the params var? I only saw it used in a few specific rule types. In which way can it affect other parts of the code?

[Skyxim]

@HolgerHuo I seem to have found another error. Originally, RULE-SET did not allow nesting of RULE-SET. It may have been lost during reconstruction. If nested, it will be impossible to determine whether the provider corresponding to RULE-SET exists.

[HolgerHuo]

It's great that those have been fixed now!