Sorry if this isn't the right place.
project will have the code split throughout several .js files. Quite possibly a library file will define functions whose
purpose is to be called from other files, but those will never be found by 'find usages' - conversely, while editing the
caller fnction, you won't be able to navigate to the definition of the lib function being called.
I propose that, as a first step, any .js files within the /web folder and subfolders be added to the internal search
tree. Later on one may think of alternate approaches.
This is implemented in 6.1.
Hi. Pardon me if I'm being obtuse, but I've been trying the daily builds and haven't been able to get code navigation
nor find usages working, not even within the same file. Is this normal (still in development), or should I file new
reports whenever it doesn't work? Thanks.
Works fine. Verified.
Yes, as of 200806111204 it's working.
move back to consistent state RESOLVED/FIXED