top-level `test.fixture` keys don't support `extname/content`
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 30/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- typescript, yaml
- 领域
- build-system
调研方向
Start by reviewing the referenced commit f53024fa6bb7e7e988c33453327f69abbdabf153 and comparing top-level test.fixture handling with fixtures in script steps. Done means the supported top-level fixture shape and any name or array behavior are decided and documented or implemented with corresponding coverage.
由索引模型根据 Issue 内容生成。
描述
https://github.com/pkgxdev/pantry/pull/4993/commits/f53024fa6bb7e7e988c33453327f69abbdabf153
it seems like fixture should work the same at the top level (or be removed? except shared fixtures would suffer.) as it does in script steps.
related: it might be useful for top-level (and even step-level) fixtures to support a name key, and an array of objects. that'd allow for:
test:
fixture:
- {
- name: a
- extname: py
- content: print("fixture a")
}
- {
- name: b
- extname: py
- content: print("fixture b")
}
script:
- python $FIXTURE_a
- python $FIXTURE_b
though we don't need this (yet). but it does provide one possible way to get rid of fixtures/props in the git repo (by moving them into the yaml). if we did this, we might want to let fixtures and props be top-level keys, so they could be segregated to the bottom to prevent visual clutter.
thoughts and ideas.
- 主要语言
- TypeScript
- 星标
- 65
- 派生
- 16
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
我们还没有检查这个项目的环境配置文件。先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
pkgxdev/brewkit 的其他 Issue
-
难度 5/5 一周以上 新手友好度 35/100
-
难度 5/5 一周以上 新手友好度 35/100
-
难度 3/5 1-2 天 新手友好度 52/100
-
难度 5/5 一周以上 新手友好度 25/100
-
难度 3/5 1-2 天 新手友好度 35/100
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
microsoft/vscode-livepreview#876 ·
维护者通常 1 天内回复
-
needs-triage
难度 1/5 1 小时以内 新手友好度 90/100
JustJarethB/invoicer#54 ·
-
ICP 1.2.0 shows a scheduled task's interval in milliseconds under the label "Interval (In seconds)"未关闭Needs Triage Type/Bug
难度 2/5 1-3 小时 新手友好度 68/100
wso2/product-integrator#2585 ·
维护者通常 1 天内回复
-
check:passed streams:add
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
design
难度 2/5 1-3 小时 新手友好度 72/100
MTES-MCT/monitor-field#119 ·
维护者通常 1 天内回复