Fill snippet gaps (asmdefs, .inputactions, UXML/USS, Render Graph feature, tests) and ship templates as a UPM package
还没有人认领这个 Issue。
评估
调研方向
Start by reviewing the existing snippets, templates, and package manifest, then compare them with the prioritized gaps in the issue. The work spans new Unity assets and a UPM package with declared dependencies. It is done when the core snippet gaps are filled and templates install through Package Manager with dependencies resolved.
由索引模型根据 Issue 内容生成。
描述
Why it matters
Snippets and templates are copy-paste starters, but the assets Unity developers struggle with most (asmdefs, Input Action assets, UXML/USS, render features) are missing entirely, and the visual-scripting "snippet" is a README. Shipping templates as a Unity package would let users import them from Package Manager with declared dependencies, which is a distribution channel inside Unity itself.
Gaps
- No
.asmdefexamples (runtime, Editor, EditMode/PlayMode Tests). - No
.inputactions, UXML or USS files. - No URP
ScriptableRendererFeature/ Render Graph pass, no HDRP shader, no Shader Graph Custom Function HLSL. - No test snippets despite the
testingskill. - No Addressables, NavMesh, Cinemachine 3, Jobs/Burst, ECS, Netcode, or UI Toolkit runtime data binding snippets.
- No real visual-scripting content (custom
UnitC# example, exported graph YAML). - Templates: no third-person, top-down, mobile, or multiplayer (NGO + Relay) starter.
Suggested approach
- Add the missing snippets, prioritizing asmdefs,
.inputactions, UXML/USS, a Render Graph renderer feature, and EditMode/PlayMode tests. - Restructure templates into a UPM package (
com.tmhsdigital.unity-dev-tools-samples) withSamples~/entries installable via a git URL, declaring dependencies inpackage.json.
Done when
Templates are importable via Package Manager with dependencies resolved, and the listed core snippet gaps are filled.
- 主要语言
- C#
- 星标
- 4
- 派生
- 0
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
TMHSDigital/Unity-Developer-Tools 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 35/100
-
ci priority: low skills
难度 3/5 1-2 天 新手友好度 55/100
-
good first issue skills testing
难度 3/5 1-2 天 新手友好度 58/100
-
ci priority: medium testing
难度 4/5 1-2 天 新手友好度 57/100
-
documentation marketing priority: medium
难度 5/5 一周以上 新手友好度 35/100
查看 TMHSDigital/Unity-Developer-Tools 的全部 Issue
相似的 Issue
-
type:task ux
难度 2/5 1-3 小时 新手友好度 72/100
elsa-workflows/elsa-foundation#5253 ·
维护者通常 1 天内回复