Chris Thomas

>In the context of dagger it makes sense though, when you decorate a property with @func, you basically ask dagger to create a function to access the field In the...

> Do you have any opinion on how we can improve this then? :D I'm open to any suggestion :) I liked the `@field()` since that is what the code...

> In my opinion, you're still hyper-focused on the dagger internals instead of giving new users a better intuitive understanding of what you know. I've found this mentality as well....

> error This project's package.json defines "packageManager": "[email protected]". However the current global version of Yarn is 1.22.22. The interesting part with `yarn` is that both `1.22.22` and `4.1.1` are actually...

The one way to solve this is to not include the dagger module in the list of yarn workspaces and give it its own `yarn.lock` file. This is far from...

> If this is true, then the solution we are discussing here might not work for the Typescript SDK. In other words, we may not have a good solution for...

I don't have dagger in my monorepo so its a little more involved for me to test. I do have packages in my monorepo though that are excluded from the...