oh shoot, you’re right. i forgot. there’s a limit on how many funs it shows. my logic was that because there are many packages then ending up with 500 results isn’t exactly helpful.
i’d be happy to hear your usecase though. myself when i want to see all Enum functions i just click on Enum and hide the sidebar to see Hexdocs own menu.
use case:
I knew there was a function in enum but forgot the name. Typed enum, scanned the list of functions but couldn’t find it and was confused.
Hiding the sidebar was something I learned about right now when you said that that was possible. I should probably have seen it if I searched a bit more…
you know what? that’s a legit problem. such a simple tool shouldn’t create so much confusion. i’ve upped the limit of resuts to an insane 1000. that shouldn’t really be hit in this scenario, but if it does at least the UI wont halt.
thanks for coming back to me.
i did something stupid. deleted a server that I didn’t use anymore. well guess what, hexdocs.krister.ee was running on it. well, I’ve restored the service, but the packages that are indexed have to be entered again. silly me.
What do you think about adding an option to hide the changelogs?
Searching for “change” you get a list of “Changelog” for every package…it makes more difficult than easier, but it’s a simple and particular scenario.
I might join the repo and check if it’s possible whenever I have some free time…
All the best and good work!
that’s a fine idea! i think adding a global filter somewhere is probably fine. pretty sure people aren’t going to use this tool to read changelogs.
Hi! Just want to add a link to our recent HexDocs Search announcement post for anyone interested.
The need for cross-package search arising from the conversation in this forum thread was one of the reasons for us to start building, so thank you all for the inspiration!
i added a small design change
so people know the menu can be hidden (and thus revealing hexdocs original menu). lol, how long did this take.
talking about https://hexdocs.krister.ee/
Nice project!
Sadly it still suffers from the same shortcomings as the original search, sometimes finding something that is not named very specific is hard.
A simple example is phoenix server-side hooks, I knew approximately how to find them because I was keeping track of new features in liveview, however it’s practically impossible to find it otherwise, unless I am missing something?
I wonder how actually hard would it be to use a pre-trained model + adding interested elixir libraries in the same manner as your project to point to correct references where it would be more forgiving about your query?
