Priority of categorizing rules

Features
1

It will be helpful if users can decide the priority of categorizing rules when matching.

2

The current prioritization is to choose the deepest sub-category.

Adding custom priorities might become very confusing and if having too many priorities things might become almost impossible to find the behavior why something is chosen first.

Better solutions I believe is to either write more specific rules or to have categories where sub-categories also need to match the category (as requested here: Having subcategories really be subcategories (partitions) of the parent category)

3

The only quibble I have there is that categories and applications aren’t always neatly tied.

For example: in my ideal case, I would have “ranked” rules, where a list of regex-based rules are applied from top to bottom in order on the current situation; the first matching rule is the one that wins, and you then specify the full category path (e.g. Programming > Editor) to apply.

This would allow me to set up my rules like this:

  1. /VSCode - blog/ → Personal > Editor
  2. /VSCode - personal-projects.*/ → Personal → Editor
  3. /VSCode/ → Work > Programming > Editor
  4. /js13k.+Slack/ → Personal > Messaging > IM
  5. /.+Slack/ → Work > Messaging > IM
  6. /Confluence/ → Work > Wiki

So you see here, I use Slack for both work and play, and VSCode for both work and play, and I want to be able to pipe specific folders/channels from those apps into the appropriate subcategories, while falling back to the appropriate subcategories under Work.

I don’t see how the current “category-first” approach will ever really let you do this.

2 Likes