Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

start DIN-SDK

未关闭
#20 7 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@Santiagocetran 已经在做这个了。

开始于 2026年7月13日。

  • #31 来自 @Santiagocetran —— 未关闭

评估

这个 Issue 还没有评估数据。

描述

Long run

Branch: feat/din-sdk (from develop)
Assignee: @Santiagocetran
Roadmap ref: P4-1.2 (CLI Integration Layer — Shared SDK Extraction) · P3-DOC7 (dind Architecture Document)

Long-running issue (expected to stay open 1–2 months). A detailed task file under Developer/tasks/ will follow — this issue tracks the overall effort, not a weekly task.

Goal

Extract the logic-dependent parts of dincli commands into a shared SDK layer at dincli/sdk/, so the same logic can be driven by both the interactive CLI and the upcoming DIN daemon (dind).

Design

  • All logic lives in dincli/sdk/. CLI command modules become thin wrappers: parse arguments → call SDK function → render output.
  • SDK functions return structured JSON outputs. This is the contract between the SDK and its two consumers:
    • the CLI reads the JSON and renders terminal UI/UX (tables, colors, human-readable messages);
    • dind reads the same JSON to update its configuration and job queue.
  • The CLI is refactored onto the SDK in this same branch — the branch is done when dincli commands run through the SDK layer and all existing tests pass.
  • No circular dependencies: SDK must be importable standalone (IPFS client, contract interfaces, wallet/account helpers, manifest loading — see P4-1.2 in Developer/ROADMAP.md for the candidate module list).

Scope

  • Inventory dincli command modules and identify which logic moves to dincli/sdk/
  • Define the JSON output schema/conventions for SDK functions (status, data, error codes)
  • Extract shared modules (IPFS, contracts, wallet/keystore, manifest/config) into the SDK
  • Refactor CLI commands to call SDK functions and render their JSON output
  • All existing tests pass; add SDK-level tests where extraction changes call paths
  • Document the public SDK interface and backward-compatibility guarantees for existing dincli commands

References

  • Developer/ROADMAP.md — P4-1.2, P3-DOC7, and the P4 phase overview ("Daemon and Agentic AI Layer")
  • Developer/issues/containerization.md — worker/container runner must be callable "from both CLI commands and future dind daemon jobs"
  • Developer/issues/validator-operations.md — daemon-mode logging/health expectations
  • Documentation/ — DIN workflow and Model workflow docs for the command surfaces being extracted

Branching note

Kept separate from the DIN daemon work (see the "start DIN daemon" issue) so the CLI-on-SDK refactor can merge into develop without waiting for the daemon. dind builds on top of this SDK's JSON interface.

主要语言
Python
星标
4
派生
7
平均合并
3 天 5 小时
30 天内合并 PR
34

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

InfiniteZeroFoundation/DevNet 的其他 Issue

查看 InfiniteZeroFoundation/DevNet 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。