A few suggestions #8997
Unanswered
yoav-lavi
asked this question in
Code Search and Navigation
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
First of all, the new code search is awesome and you should be proud.
I sent a few suggestions in the feedback window but putting them here as well:
Hiding / closing search hits would be really useful if they're not what you're looking for
The https://cs.github.com favicon is not visible on Firefox in dark mode when used as a bookmark:
(not sure this is doable) in specific cases being able to use regex as a part of a token rather than an entire token would be more convenient to avoid escaping and being visually cleaner. For example:
window./(open|close)/
vs/window\./(open|close)/
. I'm not sure this is a thing anywhere, just found myself wishing it would work in a few queries.It seems like using e.g.
language:ts
(extension based language names like you would use in a code block in markdown) works but I'm not sure the docs specify this, would be a good additionThe command palette feature (cmd + K / cmd + shift + K on https://github.com) does not seem to work in the code search, I realize both are in beta and it makes sense that the integration isn't there, but could be an interesting tool to be able to use in search
A "did you mean" feature for typos / similar tokens with results when no results are found may be useful (possibly can be done with common typos, known qualifiers that were misspelled, e.g.
lanugage:typescript
)Exporting a list of results (org - repo - file - line - character or something similar) could be useful
Excluding strings / comments from search could be useful
(More of a question than a suggestion) will this feature also be available in the mobile apps?
Thanks for your consideration!
Beta Was this translation helpful? Give feedback.
All reactions