microsoft / microsoft/agent-framework
.NET Workflows - Update object model to support structed inputs and outputs for workflow
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
Ideally this leverages existing patterns for MCS Objet Model -or- adds foundry specific contracts to AdaptiveDialog
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
Start by reviewing AdaptiveDialog and the existing MCS object model patterns mentioned in the issue. Determine the appropriate Foundry-specific contracts or reusable patterns, then verify that .NET workflows support structured inputs and outputs through the updated object model.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100