Azure / Azure/azure-functions-dotnet-worker

Design for enabling inference of collection binding without the IsBatched property

Open
#1,700 0 comments 0 reactions 0 assignees View on GitHub
design extensions team-issue
Dominant language
C#
Stars
466
Forks
215
Avg merge
3d 10h
Merged PRs (30d)
7

Description

Follow up from

- #1333

Goal of this issue is to design what inferring `IsBatched` looks like for the following extensions:

- EventGrid
- EventHub
- ServiceBus

Tasks

- [ ] Define requirements for "Batched" binding for each of these extensions
- [ ] Design an approach for setting the cardinality to "Many" without using the `IsBatched` property

Contributor guide

No contributing guide indexed for this repository

Research direction

No files or tests are named. Start by reading the follow-up issue #1333 and investigating the EventGrid, EventHub, and ServiceBus extensions. Define the batched-binding requirements for each, then document an approach for setting cardinality to "Many" without IsBatched; done means both listed tasks are resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.