Hello everyone. 👋 First post here!

[hybrid blaze]

Hey 👋

At first glance, dag.Helm isn't a valid return type. dag is an instance of a dagger.Client. The type is at dagger.Helm. That explains your error.

However, if that type comes from a dependency, you can't return types from dependencies. Only types that your module defines.

[autumn obsidian]

Thx! @hybrid blaze
I thought it was weird indeed. But looking at the documentation of this module
https://daggerverse.dev/mod/github.com/felipepimentel/daggerverse/libraries/helm@a6e2b170f4c091b039eb27100249bb19972839d7
and comparing it with other , examples show always the type (wrongly?) coming out of dag.
Are they all wrongly written?

Same for https://daggerverse.dev/mod/github.com/shykes/daggerverse/docker@c9a80c9eac0675a53a7e052da3594207f4235988
for instance
Probably I am missing out here 🤔

[hybrid blaze]

Oh, yeah it's wrong! \cc @pliant mountain @radiant fossil

We'll fix that, thanks.

They're automatically generated.

[autumn obsidian]

Of course 🙂 . What would be the proper return type then? Anything but an external type from the dependency?

[hybrid blaze]

Yes, basically.

With "anything" being under what Dagger supports, not what Python supports.

[autumn obsidian]

Sure.

THx a bunch @hybrid blaze I was very much stuck.

🙇‍♂️

(supposed to be a man bowing 🙂 )

[somber birch]

cc @left socket

Thanks Helder, likely my team will dig in.
The issue here being that the "Entrypoint" section doesn't make any sense on its own for most users?

[hybrid blaze]

No, every generated python example in the daggerverse that returns a type is using dag..

The correct prefix is dagger. but since the other SDKs don't have that prefix, it can also be removed from Python.

Or add it everywhere since it can be clearer for users.

[somber birch]

oh! not the client object dag, but this bit in the signature
def func() -> dag.Helm:
the dag.Helm

[hybrid blaze]

Yep

[somber birch]

@autumn obsidian thanks for the report. Fixed in Daggerverse!