#go.work
1 messages · Page 1 of 1 (latest)
Where does autocomplete not work on a fresh checkout for you?
I'm not utterly opposed but just wondering how much of this gets into IDE specifics
I think it's specific to working in ci and specifically sub-modules I added in ci/std/*
Oh for me std complains until I run dagger develop in it, then autocomplete/lsp/etc. all work fine
Without any go.work
mmm. Let me try that
btw dagger develop not having a recursive option can get cumbersome (we discussed this with Justin earlier)
If that's it, then I wonder if we want something more like a git hook that runs those on pull. Or just commit the generated files of course
but he was wondering if there would be any unfortunate side effects of making it recursive by default