-
Notifications
You must be signed in to change notification settings - Fork 3.7k
fix: loading of blocks with inputs. in CLI flags #8259
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.
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
Conversation
|
✅ Review Complete Code Review Summary |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
3 issues found across 19 files
Prompt for AI agents (all 3 issues)
Understand the root cause of the following 3 issues and fix them.
<file name="packages/config-yaml/src/markdown/agentFiles.ts">
<violation number="1" location="packages/config-yaml/src/markdown/agentFiles.ts:160">
Whitespace-only rules survive because trimming happens after the Boolean filter. Reverse the order or trim inside the filter to prevent empty strings from being returned.</violation>
</file>
<file name="packages/config-yaml/src/load/unroll.ts">
<violation number="1" location="packages/config-yaml/src/load/unroll.ts:249">
replaceInputsWithSecrets never rewrites the injected ${ {inputs.*} } variables, so injected blocks continue referencing inputs.* and the CLI secret rendering fix does not take effect.</violation>
</file>
<file name="extensions/cli/src/hubLoader.ts">
<violation number="1" location="extensions/cli/src/hubLoader.ts:305">
isStringRule now returns true for Windows file paths (e.g., `C:\\rules.md`), so those rules are treated as inline strings and never loaded from disk. Add the missing `"\\"` check to keep Windows paths classified as files.</violation>
</file>
React with 👍 or 👎 to teach cubic. Mention @cubic-dev-ai to give feedback, ask questions, or re-run the review.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add tests that ensure the block loading with inputs works?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No issues found across 5 files
use agent option for cn remote
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No issues found across 1 file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No issues found across 14 files
|
🎉 This PR is included in version 1.29.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 1.26.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 1.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 1.5.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
inputs.can now use fully-feature rendered secretsRearranges config loading to use the existing flow for injecting blocks for flags like --mcp and --agent model/tools etc., so that they can have secrets rendered. Replaces
inputs.withsecrets.for injected blocks, since they cannot use inputs.As a side effect, also adds file path/URI support for various flags etc.
Summary by cubic
Fixes secret rendering for blocks injected via CLI flags (--mcp, --agent model/tools) by moving injection into the main config loading flow and auto-replacing inputs.* with secrets.* for injected blocks. Removes the old enhancer and aligns services with the unified loader.
Bug Fixes
Refactors