Yep, correct! The “potentially different number” should be guarded by my traverse/preload function, where I enumerate how many parent categories does the doc have and based on that number I create the maximal c.parent.parent.parent… I was thinking a macro or something.
I really like the UI change. I kept thinking from backend perspective, but you’re definitely correct that sorting based on more than 2 categories has minor benefit.
