-
Notifications
You must be signed in to change notification settings - Fork 298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve information shown in workspace search results #62
Comments
I wonder if something weird is happening with the results, maybe #63 is related. Are you able to capture the service output when this happens? (this might be tricky until there's an option to log to file) |
@devoncarew I'm gonna do a little more testing and then do a build for 0.7. I've pushed some minor things back to 0.8 as I'd like to release the other stuff; this the only remaining case. If you can repro this or think it's potentially an issue, if you let me know before I build, I'll revert that change until 0.8. |
I went ahead and pushed 0.7. If we can repro this I can always push an update :) |
Cool; I can re-test and try and narrow down the issue this evening. |
Hmm; I had two |
Seems like a good change to me! 👍 |
That said; are we then losing the container name; eg:
Would these both appear as I think the service returns a full path of parents; maybe |
We may or may not have enough info to do this, but I think:
|
Seems reasonable, though there's also nested functions and classes; though I think always combining them (assuming we have the info) would work (eg. |
👍, makes sense |
Apparently Dart doesn't have nested classes (https://github.com/dart-lang/sdk/issues/3755)! I'll try and sort the other stuff though. |
@devoncarew What do you think about this?
|
Ugh... This looked wonky for imported packages (showed the full pub path as the location). I made a change so that it always displays the name of the last item in the |
Raised microsoft/vscode#10504 about this behaviour. I'd like to go with using the name of the last item, but this Code behaviour makes it useless. The options currently are:
Neither of these is good; so I'm gonna park this pending a response. |
Hmm, seems odd that we could display file paths w/ dots earlier, but not in this latest iteration. |
I believe all the paths we've ever displayed were by passing |
It's insanely dirty (and may fail based on the font), but replacing the dots with something that looks a bit like a dot kind works: Not sure I'm comfortable with that though 😞 |
@devoncarew I wasn't happy with this, so I've gone back and forth making lots of changes... I settled on trying to make it as similar to the document symbol list as possible (show name and parent, rather than class.member etc.). I had to do some gymnastics to make filenames display nicely (discussion here). If you get a min, can you take a look (it's in master) and see if it seems to behave and display reasonably? |
I'll take a look; from a brief glance, I see the long paths in the display. It might be nice to display package refs as |
That issue w/ truncating everything before the last dot is really annoying :) |
FYI, I don't see the truncating issue in the latest VSCode Insiders build. |
Hmm, disregard the above. |
Hmm, could you give an example? Or maybe breakpoint/log in the
Yeah, I really wanted to do that but thought I didn't have the required info; but now I'm wondering if what I've already done handles that... Maybe I'll take a stab at this tomorrow evening (though you're free to have a stab if you wish).
I figured with the symlinks gone,
Tell me about it! :D I spent so long today just going back and forth trying to make this work.. But, where were you seeing it - the code I pushed shouldn't show that anymore (or were you tweaking the code?)
Interesting! Maybe I should install it. I didn't realise it worked side-by-side, so probably makes sense. I don't mind shipping known issues like the filenames being wonky if it'll fix itself in the next Code update! Oh, just saw your comment on the MS case; does still happen :( |
The crazy behaviour with stripping stuff has gone, so should indeed be fixed in Insiders (that's nightly?). We should just assume veryone will soon update, so if it shows something weird in the meantime, so be it! |
We should tweak this to not rely on |
Moved last comment to #95; I think it's an edge case. |
I think this is a result of merging two API call results?
The text was updated successfully, but these errors were encountered: