-
Notifications
You must be signed in to change notification settings - Fork 1
Fix/pipeline exports #395
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
base: main
Are you sure you want to change the base?
Fix/pipeline exports #395
Conversation
|
Important Review skippedToo many files! 150 files out of 300 files are above the max files limit of 150. You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
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".
| export * from './runner'; | ||
| export { OFFICIAL_EXTENSION_BLUEPRINTS } from './official'; | ||
| // Export official blueprints from a dedicated entry point to avoid bundling them | ||
| // with core logic (they contain large documentation strings). | ||
| export type { |
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.
Restore OFFICIAL_EXTENSION_BLUEPRINTS export from extensions entry
The @wpkernel/pipeline/extensions entry point no longer re-exports OFFICIAL_EXTENSION_BLUEPRINTS (lines 1‑4 now only export types). Any consumer following the documented import import { OFFICIAL_EXTENSION_BLUEPRINTS } from '@wpkernel/pipeline/extensions' will now fail to resolve that symbol even though the package still publishes the extensions entry. Unless this entry point is intentionally deprecated, the documented API is broken and needs the constant re-exported (or the docs/exports updated) to avoid runtime/module resolution errors.
Useful? React with 👍 / 👎.
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. ℹ️ You can also turn on project coverage checks and project coverage reporting on Pull Request comment Thanks for integrating Codecov - We've got you covered ☂️ |
No description provided.