microsoft / microsoft/agent-framework
.NET Workflows - Ensure `DeclarativeActionCompletedEvent` is raised for every action
Open
Nobody has claimed this yet.
.NET
declarative
workflows
- Dominant language
- Python
- Stars
- 13.6k
- Forks
- 2.3k
- Avg merge
- 2d 45m
- Merged PRs (30d)
- 358
Description
`DeclarativeActionCompletedEvent` is skipped for parent actions for `goto` and `endworkflow` actions that bypass the default terminal edge of the parent action.
Has potential impact on workflow designer.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the .NET workflow implementation that raises DeclarativeActionCompletedEvent, then trace how parent actions are completed when goto and endworkflow bypass the default terminal edge. Confirm the event is raised for every action, including those parent-action paths, and add or update coverage if the relevant tests are found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100