schemas create --dry-run doesn't validate anything, just echoes input back
还没有人认领这个 Issue。
评估
调研方向
Look at the schemas create command implementation, likely in a commands/ or schemas/ directory. Compare it with schemas update --dry-run to see how the API validation is called. The fix involves ensuring the dry-run path performs the same validation as the real execution. Run the failing test cases from the issue description to verify the fix.
由索引模型根据 Issue 内容生成。
描述
Version: hubspot 0.14.0 (build 1162, commit unknown)
Command run:
$ echo '{}' | hubspot schemas create --dry-run
$ echo '{"name":"test_object_xyz"}' | hubspot schemas create --dry-run
Expected result: given schemas create (without --dry-run) rejects both of these bodies with a 400 validation error (Some required fields were not set: [name, labels], then [labels]), the --dry-run equivalent should surface the same validation problem rather than reporting success.
Actual result: --dry-run reports ok: true for both, regardless of body content, simply echoing back whatever was piped in:
$ echo '{}' | hubspot schemas create --dry-run
{"ok":true,"executed":false,"dry_run":true,"data":{}}
$ echo '{"name":"test_object_xyz"}' | hubspot schemas create --dry-run
{"ok":true,"executed":false,"dry_run":true,"data":{"name":"test_object_xyz"}}
$ echo '{}' | hubspot schemas create
{"ok":false,"error":{"status":400,"message":"Invalid input JSON on line 1, column 2. Some required fields were not set: [name, labels]"}}
For comparison, schemas update --dry-run genuinely calls the API - it returns portal-specific data (state_snapshot, digest, the actual portal ID), so this isn't true of every --dry-run in the CLI, just schemas create (and possibly other create commands - not exhaustively tested).
Why this matters: the README's own beta warning recommends using --dry-run before mutations as the safety practice for a tool that can modify live CRM data. For schemas create, a passing dry-run gives no assurance the real call will succeed.
- 主要语言
- 没有语言数据
- 星标
- 7
- 派生
- 2
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
HubSpot/agent-cli 的其他 Issue
-
properties get/list/batch-read appear unable to retrieve sensitive or highly-sensitive properties未关闭
难度 3/5 1-2 天 新手友好度 68/100
-
难度 3/5 1-2 天 新手友好度 65/100
-
难度 4/5 3-5 天 新手友好度 48/100
查看 HubSpot/agent-cli 的全部 Issue
相似的 Issue
-
black --check exits 0 and prints All done when a multi file run is interrupted可能已有人在做 @jiteshgulati 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 2 天内回复
-
README for cli可能已有人在做 @Janvi-kapoor 今天认领。 未关闭OSCI'26
难度 2/5 1-3 小时 新手友好度 70/100
GauravKarakoti/SecureFlow#1308 · 1 条评论 ·
维护者通常 1 天内回复
-
bug discussion
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
ajeetdsouza/zoxide#1323 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 2/5 1-3 小时 新手友好度 70/100
graygarbage/HermesKey#21 ·