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 #146] [CLOSED] Refactor event api for consistency and flexibility #161

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

📋 Pull Request Information

Original PR: https://github.com/run-llama/workflows-py/pull/146
Author: @adrianlyjak
Created: 10/16/2025
Status: ❌ Closed

Base: main ← Head: cursor/LI-3867-refactor-event-api-for-consistency-and-flexibility-dc87

📝 Commits (1)

  • 506e4d2 Refactor event handling and start event parsing

📊 Changes

1 file changed (+108 additions, -28 deletions)

View changed files

📝 src/workflows/server/server.py (+108 -28)

📄 Description

Refactor event data API to standardize input formats and provide richer type metadata for events, ensuring backward compatibility.

The existing event API had inconsistencies in input formats (data vs value, qualified names vs short names) and lacked sufficient type metadata for clients to easily identify event hierarchies (e.g., StopEvent, InputRequiredEvent). This PR implements Adrian's proposal to standardize input formats, introduce type and types metadata in event envelopes, and enhance event resolution, making the API more robust and user-friendly.

Linear Issue: LI-3867

Open in Cursor Open in Web

🔄 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/146 **Author:** [@adrianlyjak](https://github.com/adrianlyjak) **Created:** 10/16/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `cursor/LI-3867-refactor-event-api-for-consistency-and-flexibility-dc87` --- ### 📝 Commits (1) - [`506e4d2`](https://github.com/run-llama/workflows-py/commit/506e4d247ec26d9f01dd07579079f9f5d8cb31ff) Refactor event handling and start event parsing ### 📊 Changes **1 file changed** (+108 additions, -28 deletions) <details> <summary>View changed files</summary> 📝 `src/workflows/server/server.py` (+108 -28) </details> ### 📄 Description Refactor event data API to standardize input formats and provide richer type metadata for events, ensuring backward compatibility. The existing event API had inconsistencies in input formats (`data` vs `value`, qualified names vs short names) and lacked sufficient type metadata for clients to easily identify event hierarchies (e.g., `StopEvent`, `InputRequiredEvent`). This PR implements Adrian's proposal to standardize input formats, introduce `type` and `types` metadata in event envelopes, and enhance event resolution, making the API more robust and user-friendly. --- Linear Issue: [LI-3867](https://linear.app/llamaindex/issue/LI-3867/event-data-api-refactor) <a href="https://cursor.com/background-agent?bcId=bc-e2cddf2d-bc51-4c28-9c83-c1a712c59218"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/open-in-cursor-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/open-in-cursor-light.svg"><img alt="Open in Cursor" src="https://cursor.com/open-in-cursor.svg"></picture></a>&nbsp;<a href="https://cursor.com/agents?id=bc-e2cddf2d-bc51-4c28-9c83-c1a712c59218"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/open-in-web-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/open-in-web-light.svg"><img alt="Open in Web" src="https://cursor.com/open-in-web.svg"></picture></a> --- <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:46 -05:00
yindo closed this issue 2026-02-16 02:16:46 -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#161
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?