Is there a good recommended workflow for

[hollow stag]

Also abit awkward if I want to iterate on a daggerverse module that's already pushed ...

  "dependencies": [
    {
      "name": "golangcilint",
      "source": "github.com/papercomputeco/daggerverse/golangcilint@main",
      "pin": "8646f8127d0bb464437e12f0a5d83d72edc211d8"
    }
  ],

would be amazing if there was a dagger install override command that could provision an override locally in something like dagger.override.json. Maybe something like:

{
  overrides: [
    {
      source: github.com/papercomputeco/daggerverse/golangcilint@main,
      replace: ../daggerverse/golangcilint
    }
  ]
}

then I could also add that override to gitignore and keep remote clean.

[gilded thistle]

Agree its a bit awkward. A replace would be cool but at the moment it can't escape the git context.

One thing I do for modules that really need testing is use the example to exercise the happy paths https://github.com/kpenfound/dag/blob/main/artifactory/examples/go/main.go
These also get rendered in daggerverse as long as they're named correctly

[hollow stag]

Hmm gotcha! Consider me an advocate for a dependency override feature or absolute path resolution in deps! I've generally left out examples and tests in my daggerverse modules since it ends up being alot of Go boilerplate. For example, this one I'll likely hoist out but probably isn't worth its own example/test harness:

https://github.com/papercomputeco/tapes/blob/main/.dagger/tidy.go

[hollow stag]

Hit some nasty snags that may have been easily caught with a nice local dev flow:

❯ dagger call --help
✔ connect 0.5s
✘ load module: . 0.7s ERROR
✘ loading type definitions 0.1s ERROR
! main object not found, check that your module's name and main object match

I had already pushed this up and was getting an all green build on dagger install and dagger develop ... but the module wasn't there! Would be very ideal if dagger install failed if the module was invalid!

[unique crater]

upcoming workspaces seem like the perfect place to configure replace directives... 🙂 #1468070450524459029

[neat umbra]

Hi 👋

Taking a go today about it, thanks for the feedback 👼

[hollow stag]

Ooo modules v2 👀 y’all’s cookin

[unique crater]

If I understand correctly, dagger install silently installed a module that fails to load? I find that surprising! But maybe it's a regression we introduced when we made module loading lazy