dagger development linter/scanning

[hallow quartz]

Curious. In the past we chatted about the cool progress that trunk.io was making and it's a really useful tool for precommit/fmt/linting. I don't think ya'll ended up using them and use custom tooling like markdownlint and golangci-lint in your own custom tooling.

Curious about the experience.

Trunk:

• integrates with editor (can be your formatter and report code problems)
• sealed and has runtimes
• community + company regularly maintained and mapped linting/tooling. Not containerized.
• free but for enterprise/private internal usage it's subscription.
• focused on local dev workflow
  Dagger
• have to roll your own for everything, free
• not integrated with editor
• focused more on the build/release with some perks for local

*** This is context of the local development toolchain, not CI *** Big fan so I'm weighing out how they approach this.

Curious how you've weighed out dogfooding dagger when there's other tooling in the space. Dagger's local developer experience is different as it's all self contained, but with local development that's not quite the right fit.

So yes random thread to just see if any of you have weighed out where dagger fits in the context of local development tooling and where it doesn't.

another example:

• local test: probably better with gotestsum/gotest
• local test with integration dependencies dagger as the services and such can all be coordinated now by dagger in CI + remote the same way.

[errant lark]

Heya, not sure I can answer every question here but! I'll try my best.

So what we're trying to do is to give a unified experience between local+automated CI environments - running your tests/lints/formatting/etc shouldn't be a completely different experience in different places. Containerization is a big part of that - without that, it becomes much harder to reason about what dependencies are where, and to reproduce the same results in both places.

There's no editor integration today AFAICT - but I don't think there's any major blockers to doing something like that if anyone was interested - it would be super cool to automatically connect dagger functions into a little side-panel, but I think we're focusing on the core CLI at the moment, and iterating on getting that experience as good as it can be first!

Personally, I really want to try using dagger to wrap every part of my local dev experience 😄 I'd love to have dagger be the entrypoint for testing/linting/codegen/etc - we're working on that process for our own CI in https://github.com/dagger/dagger/pull/6843, which isn't quite there, but I'm picking this up later this week! (after spending the week at kubecon 😅)