Let business code use the temporalx event helpers - #106
Merged
Merged
Conversation
The wired-in-main rule predates the helpers the event catalog assigns to temporalx: Tracer, WorkflowEvent and WorkflowFailed exist for workflow, activity and dispatcher code. Construction stays in main.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Amends the
AGENTS.mdrule "obsx, temporalx and migratex are wired in main() only": temporalx's workflow-side helpers (Tracer,WorkflowEvent,WorkflowFailed) are meant for workflow/activity/dispatcher code — the RFC-0031 event catalog assigns those events to temporalx. Construction stays inmain(). Docs only.🤖 Generated with Claude Code
https://claude.ai/code/session_018N7ME8TyWS33cbpWV3v8E8