Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Basic Module support #3

Open
wingyplus opened this issue Jun 2, 2024 · 0 comments · May be fixed by #7
Open

Basic Module support #3

wingyplus opened this issue Jun 2, 2024 · 0 comments · May be fixed by #7
Labels
enhancement New feature or request

Comments

@wingyplus
Copy link
Owner

wingyplus commented Jun 2, 2024 •
edited
Loading

After finish the codegen, we can implement the dagger module on the root repository to conform the module runtime interface.

Scopes

  • dagger init --sdk=<our runtime> should works by generating a project including binding the dependencies and the code example should follow the official SDK.
  • dagger functions can see the functions from within module. The documentation can be blank at this state.
  • dagger develop should works
  • dagger call on the code example, generated by dagger init should works.
  • List all follow-ups issues.
@wingyplus wingyplus linked a pull request Jun 22, 2024 that will close this issue
Draft
9 tasks
@wingyplus wingyplus changed the title Module support Basic Module support Jun 30, 2024
@wingyplus wingyplus added the enhancement New feature or request label Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

module support wingyplus/dagger-dotnet-sdk
1 participant
@wingyplus