Skip to content

refactor: migrate from content-based to event-based communication model - #446

Merged
tusharmath merged 2 commits into
mainfrom
add-diff-output-to-apply-json
Mar 4, 2025
Merged

refactor: migrate from content-based to event-based communication model#446
tusharmath merged 2 commits into
mainfrom
add-diff-output-to-apply-json

Conversation

@tusharmath

Copy link
Copy Markdown
Collaborator

Description

This PR refactors the communication model in forge to use explicit events instead of raw content strings. The change makes the event flow more explicit across the system and simplifies the codebase.

Changes

  • Replace ChatRequest.content with Event object
  • Simplify ForgeExecutor by removing environment and tool services
  • Move event type constants from domain layer to UI layer
  • Update Orchestrator to use direct event dispatch
  • Add input field to Transform::User for bidirectional communication
  • Update tests and integration to use new event-based API

Testing

Most tests pass, though there are some integration test failures related to tracing initialization which should be addressed separately. These failures are not directly caused by the code changes in this PR.

Additional Notes

This refactoring is part of a larger effort to simplify the system architecture and make the code more maintainable.

@github-actions github-actions Bot added the type: chore Routine tasks like conversions, reorganization, and maintenance work. label Mar 4, 2025
This PR refactors the communication model in forge to use explicit events instead of raw content strings. Key changes include:

- Replace ChatRequest.content with Event object
- Simplify ForgeExecutor by removing environment and tool services
- Move event type constants from domain layer to UI layer
- Update Orchestrator to use direct event dispatch
- Add input field to Transform::User for bidirectional communication
- Update tests and integration to use new event-based API

This refactoring simplifies the code and makes the event flow more explicit across the system.
@tusharmath
tusharmath force-pushed the add-diff-output-to-apply-json branch from 234c07e to 743b254 Compare March 4, 2025 07:55
@tusharmath
tusharmath merged commit a13c657 into main Mar 4, 2025
@amitksingh1490
amitksingh1490 deleted the add-diff-output-to-apply-json branch November 14, 2025 10:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: chore Routine tasks like conversions, reorganization, and maintenance work.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant