You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Python SDK, the signatures of Directory.with_new_file and Container.with_new_file are inconsistent. For Directory, contents is a required positional argument, while for Container, contents is a keyword-only argument. This inconsistency is confusing and often requires referencing the API documentation to determine the correct usage. I vote for setting up a PR, if you could give me a hint on the preferred behaviour.
Yeah, that's a good point. I think the Directory version, with contents being a required argument is preferred, but it's not a Python change, it's a core API change.
What is the issue?
In the Python SDK, the signatures of
Directory.with_new_file
andContainer.with_new_file
are inconsistent. ForDirectory
,contents
is a required positional argument, while forContainer
,contents
is a keyword-only argument. This inconsistency is confusing and often requires referencing the API documentation to determine the correct usage. I vote for setting up a PR, if you could give me a hint on the preferred behaviour.Dagger version
dagger v0.10.2 (registry.dagger.io/engine) darwin/arm64
Steps to reproduce
No response
Log output
No response
The text was updated successfully, but these errors were encountered: