Support of Term ID (with depth)" argument.

could you provide more info on the use case. Sounds like you just want view_alias to pick up views that use the TermID (with depth) OR TermID. There is no expectation that a Term ID with depth is useful to the alias right?

What value does the depth add to the alias? Wouldn't the resulting alias have the same URL?

This is how I think it would work. The depth argument determines how many parents up the chain to include in the URL. That is, given a taxonomy with term 'Foo' (tid 1), 'Foo' has one child term 'A' (tid 2). and 'A' has three child terms 'alpha', 'beta', and 'gamma', (tids 3 - 5, respectively), then a term argument with depth 1 would generate the following URLs:

* my-page-view/1 => my-page-view/Foo
* my-page-view/2 => my-page-view/Foo/A
* my-page-view/3 => my-page-view/A/alpha
* my-page-view/4 => my-page-view/A/beta
* my-page-view/5 => my-page-view/A/gamma

I'm not sure what negative depths would do. The same? Reverse the order of the terms?

Thoughts?

We leverage the taxonomy term tokens to generate the paths. For parent terms, there isn't a token that limits itself to n parents. What is available is [term:parents:join:?], so we use this to add ALL parents whenever the depth is non-zero with the token string: my-page-view/[term:parents:join:/]/[term:name]

I'm going to mark this closed and open up additional feature request issues to cover everything else.