feat(framework): export param types fixes NV-7261#10407
Conversation
✅ Deploy preview added
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe public API is extended by re-exporting four types— Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What changed? Why was the change needed?
What changed
The framework now exports four commonly-used types from its public API:
StepResolverContext,ContextResolved,Subscriber, andExecuteInput. These types are essential for developers using the framework to properly type their step resolvers and workflow implementations. TheStepResolverContexttype was marked for export at its definition point, and all four types are now re-exported from both the main entry point and the step-resolver module for easier access.Affected areas
@framework: Types are now exported from
packages/framework/src/index.tsandpackages/framework/src/step-resolver.ts, making them available to developers building workflows and step resolvers with the framework.Testing
No tests were added, as type exports do not require runtime testing — TypeScript compilation validates that the types are correctly defined and exported.
Screenshots
Expand for optional sections
Related enterprise PR
Special notes for your reviewer