Repository navigation
Expose TaskRunnerReturn and refactor related types - #15
Conversation
- Export `TaskRunnerReturn` to make it part of the public API. - Move `TaskRunnerReturn` definition near `TaskStateEnd` for better organization. - Use `TaskRunnerReturn` in `SyncRunner`, `AsyncRunner`, and `resolveEndState` to ensure consistency.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
Exposed the
TaskRunnerReturntype inmain.tsand updatedSyncRunner,AsyncRunner, andresolveEndStateto use it consistently. This improves the public API and maintainability by centralizing the task runner return type definition. Verified with tests and linting.PR created automatically by Jules for task 4692193095878845712 started by @Mopsgamer