Previously the dependency kind "test" was not accepted by the dependencies logic, so test files were not indexed. This affected jumping between tags inside tests - since no ctags were generated for these files, there usually weren't tags to jump to.
I actually came across this from a slightly different angle: I have a workspace that has a root project containing only integration tests, i.e. no lib or bin types. So rusty-tags was not able to find the root project package because it had the following targets:
Previously the dependency kind "test" was not accepted by the dependencies logic, so test files were not indexed. This affected jumping between tags inside tests - since no ctags were generated for these files, there usually weren't tags to jump to.
I actually came across this from a slightly different angle: I have a workspace that has a root project containing only integration tests, i.e. no
lib
orbin
types. So rusty-tags was not able to find the root project package because it had the following targets:Therefore the
updater
package never got added to the dependencies list, leading to a later errorCouldn't find package for (updater, 0.1.0)
So this could be taken as a "feature" or a "bugfix" - kind of both. Let me know if you'd like me to reword anything.