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

Expand output binding documentation #39009

Closed
gani-simsek opened this issue Dec 31, 2024 · 3 comments
Closed

Expand output binding documentation #39009

gani-simsek opened this issue Dec 31, 2024 · 3 comments
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. Docs Functions issue-addressed Workflow: The Azure SDK team believes it to be addressed and ready to close. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@gani-simsek
Copy link

Type of issue

Missing information

Description

There is insufficient documentation regarding how the Out class methods work, in particular the set method.

What kinds of objects are accepted? Experience, and common sense, tells me obviously not every object. What can I pass them as input? How are those objects handled?

I am looking for the actual implementation code per output binding type and I couldn't find the documentation anywhere. Azure documentation on functions is just entry level tutorials with simple examples.

Please add implementation details to this page or add link to the GitHub code if it somewhere in there. As a developer, I want to know how these bindings work under the hood, so I can make an informed decision if I should use them or implement my own.

Page URL

https://learn.microsoft.com/en-us/python/api/azure-functions/azure.functions.out?view=azure-python

Content source URL

https://github.com/MicrosoftDocs/azure-docs-sdk-python/blob/main/docs-ref-autogen/azure-functions/azure.functions.Out.yml

Document Version Independent Id

5d8361bb-f64d-9986-5170-31b40c6e452a

Article author

@lmazuel

Metadata

  • ID: 8db2d4f5-1e34-43ea-7dfa-c94e5a519477
  • Service: azure-functions
@github-actions github-actions bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Dec 31, 2024
@xiangyan99 xiangyan99 added Docs Service Attention Workflow: This issue is responsible by Azure service team. Functions and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Jan 1, 2025
@github-actions github-actions bot added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Jan 1, 2025
Copy link

github-actions bot commented Jan 1, 2025

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @ahmedelnably @fabiocav.

@kashifkhan kashifkhan added the issue-addressed Workflow: The Azure SDK team believes it to be addressed and ready to close. label Jan 2, 2025
@kashifkhan
Copy link
Member

@gani-simsek this issue needs to be opened in the azure-functions repo which is here https://github.com/Azure/Azure-Functions. This repo is for the azure python sdks.

@github-actions github-actions bot removed the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Jan 2, 2025
Copy link

github-actions bot commented Jan 2, 2025

Hi @gani-simsek. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. Docs Functions issue-addressed Workflow: The Azure SDK team believes it to be addressed and ready to close. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

3 participants