run-llama/workflows-py
1
0
Fork 0
mirror of https://github.com/run-llama/workflows-py.git synced 2026-07-20 19:57:02 -04:00
Code Issues 18 Packages Projects Releases 10 Wiki Activity

[PR #126] [MERGED] Expose workflow events in server and workflow class #144

New Issue
Closed
opened 2026-02-16 02:16:43 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 02:16:43 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/run-llama/workflows-py/pull/126
Author: @logan-markewich
Created: 10/6/2025
Status: ✅ Merged
Merged: 10/8/2025
Merged by: @logan-markewich

Base: main ← Head: logan/expose_workflow_events

📝 Commits (5)

  • 1c17f9a expose workflow events in Workflow class and server
  • 72747dc expose workflow events in Workflow class and server
  • 8554346 add test
  • 0e56e07 improve tests
  • 5caffbe fix tests

📊 Changes

3 files changed (+109 additions, -1 deletions)

View changed files

📝 src/workflows/server/server.py (+64 -1)
📝 src/workflows/workflow.py (+32 -0)
📝 tests/test_workflow.py (+13 -0)

📄 Description

  • adds a workflow.events property to return a list of all known event types
  • exposes /workflows/{name}/events in WorkflowServer to get event schemas
  • adds additional_events param to server.add_workflow() for cases where events are needed beyond what type annotations expose (like special events needed for ctx.wait_for_event())

The motivation for this is to enhance UI's like the workflow debugger, which would benefit from these schemas when exposing a send_event() UI component

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/run-llama/workflows-py/pull/126 **Author:** [@logan-markewich](https://github.com/logan-markewich) **Created:** 10/6/2025 **Status:** ✅ Merged **Merged:** 10/8/2025 **Merged by:** [@logan-markewich](https://github.com/logan-markewich) **Base:** `main` ← **Head:** `logan/expose_workflow_events` --- ### 📝 Commits (5) - [`1c17f9a`](https://github.com/run-llama/workflows-py/commit/1c17f9ad722f97f235a08d50cc32323dd4f64d99) expose workflow events in Workflow class and server - [`72747dc`](https://github.com/run-llama/workflows-py/commit/72747dc73341ffaf098812cc03fe9e62c1a2371b) expose workflow events in Workflow class and server - [`8554346`](https://github.com/run-llama/workflows-py/commit/85543464220c16ff0b7272ae79cb3798f15371e1) add test - [`0e56e07`](https://github.com/run-llama/workflows-py/commit/0e56e070ee062fcc040d4116d2d0e3c04c21bae2) improve tests - [`5caffbe`](https://github.com/run-llama/workflows-py/commit/5caffbef9592205a70d9d00090117fff734bd1db) fix tests ### 📊 Changes **3 files changed** (+109 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `src/workflows/server/server.py` (+64 -1) 📝 `src/workflows/workflow.py` (+32 -0) 📝 `tests/test_workflow.py` (+13 -0) </details> ### 📄 Description - adds a `workflow.events` property to return a list of all known event types - exposes `/workflows/{name}/events` in `WorkflowServer` to get event schemas - adds `additional_events` param to `server.add_workflow()` for cases where events are needed beyond what type annotations expose (like special events needed for `ctx.wait_for_event()`) The motivation for this is to enhance UI's like the workflow debugger, which would benefit from these schemas when exposing a `send_event()` UI component --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-16 02:16:43 -05:00
yindo closed this issue 2026-02-16 02:16:43 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
enhancement
good first issue
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/workflows-py#144
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?