I like this! It would be great if it was a hosted solution where I could just add any repository to the URL, like https://pkg.go.dev/ does for the godocs.
joe-esquibel 3 hours ago [-]
Whats the validation strategy that you used for this? I run a similar project and I found that golden repos were needed to prevent drift. Have you stress tested this to find any limits? I compared my go work to ctags and treesitter for proof of functions found and list precision and recall.
RamblingCTO 2 hours ago [-]
> Every Go package in github.com/peterretief/yggstore, what it builds on, and the functions in each of its files. Tests are left out.
it's a cool idea, but reads super sloppy, sorry. There is literally no effort in this.
gchamonlive 2 hours ago [-]
It's ironic you didn't put any effort into calling out the lack of effort put in the project. Btw, the project README is fine, this is AIslop hysteria.
RamblingCTO 44 minutes ago [-]
And what would effort look like, besides inspecting code and the result to find the message I quoted, huh?
gchamonlive 35 minutes ago [-]
Idk, the project looks good to me, you are the one making claims and not backing them up properly. To me you just disagree with this specific aesthetic choice and are lazily extrapolating to the rest of the project just in case the comment could catch some upvotes.
peter_retief 2 hours ago [-]
It is just the idea, for me to navigate my project code, free to use and change
baalimago 4 hours ago [-]
Interesting! It would be cool to see this as a cli tool to allow agents to efficiently inspect codebases
dmoose 3 hours ago [-]
I took a bit different approach assuming that agents can use the language servers to get structure and just trying to keep them honest. With this in a hook a lot of stuff is caught quickly without wasting a lot of context. https://github.com/dmoose/gochecks
3 hours ago [-]
slantedview 4 hours ago [-]
This is really cool. I could see adding this alongside the godocs to my open source projects.
tortela 2 hours ago [-]
would be nice if there was a picture of the final result in the README.md
I can see this approach being useful across non-Go repositories too.
[0] https://dev.fast/
[1] https://github.com/pingdotgg/t3code
it's a cool idea, but reads super sloppy, sorry. There is literally no effort in this.