You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sort of like nested categories, except limit it to 2 or 3 deep (ie, main and secondary (2 deep) or a third level max).
Benefit would be multiple "Must (Not) Contain" filters either when one isn't enough (or would be very complex to do singularly), or when needing similar filters for multiple rules that have minor differences in them being applied to different feeds.
Of course, in order for the nested rules to work, the root rule must be active. The top level rule would be a regular rule, treated normally, with the nest rules being independent beyond the "Must (Not) Contain" matches. (Nested rules can use feeds independent of the top level rule, for example.)
Use case
A site I use will sometimes have a bunch of older episodes of shows with many seasons being added to the feed. To prevent downloading those older episodes, I include as part of the "NOT" matching the name of the show and some regex to catch those older seasons. I also like to match multiple different criteria for what to accept and want to control which category each goes to. As it is now, have to copy/paste the matching (or excluding) information to each rule. But nesting it would allow one rule to do it all, with sub rules only needing to match what comes through.
Extra info/examples/attachments
Primary:
INC: (1080p|2160p)
EXC: Show Name s[01]/de\d\d
Secondary-1:
INC: (HEVC|[hx]265)
CAT: 265
Secondary-2:
INC: x264
CAT: 264
The text was updated successfully, but these errors were encountered:
Suggestion
Sort of like nested categories, except limit it to 2 or 3 deep (ie, main and secondary (2 deep) or a third level max).
Benefit would be multiple "Must (Not) Contain" filters either when one isn't enough (or would be very complex to do singularly), or when needing similar filters for multiple rules that have minor differences in them being applied to different feeds.
Of course, in order for the nested rules to work, the root rule must be active. The top level rule would be a regular rule, treated normally, with the nest rules being independent beyond the "Must (Not) Contain" matches. (Nested rules can use feeds independent of the top level rule, for example.)
Use case
A site I use will sometimes have a bunch of older episodes of shows with many seasons being added to the feed. To prevent downloading those older episodes, I include as part of the "NOT" matching the name of the show and some regex to catch those older seasons. I also like to match multiple different criteria for what to accept and want to control which category each goes to. As it is now, have to copy/paste the matching (or excluding) information to each rule. But nesting it would allow one rule to do it all, with sub rules only needing to match what comes through.
Extra info/examples/attachments
The text was updated successfully, but these errors were encountered: