-
Notifications
You must be signed in to change notification settings - Fork 1
Phase 9: unblock readiness factory typing #375
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
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.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex 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.
💡 Codex Review
wp-kernel/packages/cli/src/commands/create.ts
Lines 140 to 147 in 92c110b
| override async execute(): Promise<WPKExitCode> { | |
| return this.executeInitCommand({ | |
| commandName: 'create', | |
| reporterNamespace: buildReporterNamespace(), | |
| dependencies: dependencies.runtime, | |
| ensureGeneratedPhpClean: dependencies.ensureGeneratedPhpClean, | |
| hooks: buildCreateCommandHooks(this, dependencies), | |
| }); |
wpk create ignores readiness helpers provided via config
readiness.helpers factories from the project config are passed into runCommandReadiness for apply and generate, but the create command never forwards them. The call to executeInitCommand (lines shown) constructs readiness hooks, yet the runtime options it supplies omit config.readiness?.helpers, so createInitCommandRuntime builds a registry with only the built‑ins. A project defining custom readiness helpers in its config will therefore never see them executed when running wpk create. To keep command behaviour consistent with the new configuration API, propagate helperFactories from the loaded config when preparing the create command’s readiness phase.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review |
|
Codex Review: Didn't find any major issues. Bravo. ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Summary
Testing
Codex Task