Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SDK-Bindings - Queue] Implement QueueMessage converter #1444

Closed
3 of 4 tasks
liliankasem opened this issue Mar 30, 2023 · 2 comments · Fixed by #1470
Closed
3 of 4 tasks

[SDK-Bindings - Queue] Implement QueueMessage converter #1444

liliankasem opened this issue Mar 30, 2023 · 2 comments · Fixed by #1470
Assignees

Comments

@liliankasem
Copy link
Member

liliankasem commented Mar 30, 2023

Problem Statement

Implement QueueMessageConverter to enable binding to the QueueMessage, BinaryData and JObject types so that we have parity with in-proc.

Tasks

  • Implement converter that enables binding to a single QueueMessage, BinaryData and JObject
  • Write unit tests for converter and support parts
  • Write E2E tests for queue trigger function with QueueMessage binding
  • Release Queue worker extension package

Definition of Done

  1. Worker Storage.Queue extension package is released (as a preview package) with support for binding to a QueueMessage, BinaryData, and JObject
  2. Unit & E2E tests written and checked-in
  3. Microsoft documentation updated to detail support for the new SDK-bindings
@fabiocav
Copy link
Member

Moving to sprint 145, but we're currently blocked on the WebJobs extension release and the deferred binding changes.

@fabiocav
Copy link
Member

Still blocked on the WebJobs changes. Moving to 147, assuming that dependency will be closed by then.

@fabiocav fabiocav removed this from the Functions Sprint 147 milestone Jun 17, 2023
@liliankasem liliankasem removed the blocked Items that cannot move forward at the moment. label Jun 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants