-
Notifications
You must be signed in to change notification settings - Fork 93
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
Search on extension #160
Comments
Certainly it is possible. So one of the issues with this is that the number of extensions grows as a massive rate. I implemented this on searchcode.com and you run into the situation of what to do with things like Dockerfiles which have no extension. Do you treat the whole thing as an extension? What about files with multiple periods in them, for example typings.d.ts Its something I am looking at doing. What might work better though is that if #158 was implemented and if you could easily see what files are categorised as "Unknown" and easily add them to be classified correctly. |
In my case no extantion means really old fortean :) Maybe reverse filename
then. It would allow to search for ts.d.* for such typescript files? Just
late night idea ;)
|
Actually the reversed filename is a dammed good idea. |
reindexing... if asterisk is in the middle, you know prefix and postfix already, so such search is not needed,
I will play a bit with this as I may talk nonsense |
Agreed but I would need a solution to the above. Its something that if I can get a good solution to I will implement. |
Maybe it would be possible to introduce similar to fn parameter for extension, like:
fe - File extension. E.G. fe:cs
I'm fighting with unknown types and it would be great to be able to determine scope of each
The text was updated successfully, but these errors were encountered: