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

[wip] feat: new azure-functions-streaming preset #2477

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

supersoniko
Copy link

@supersoniko supersoniko commented May 28, 2024

🔗Linked issue

#2478

❓Type of change

  • 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • 👌 Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Added a preset azure-functions-streaming which adds support for the Azure Functions V4 runtime with HTTP Streaming enabled. This allows applications (like Solid Start) that require HTTP Streaming to now work properly on Azure Functions.

I also upgraded the @azure/functions package to the latest version, which is required to support this functionality.

📝 Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@supersoniko supersoniko changed the title [wip\ feat: new azure-functions-streaming preset [wip] feat: new azure-functions-streaming preset May 28, 2024
@supersoniko
Copy link
Author

To do: Update regular azure-function preset to v4

@pi0 pi0 marked this pull request as draft May 28, 2024 22:21
@pi0
Copy link
Member

pi0 commented May 28, 2024

Thanks for working on this dear Sacha. For now i have marked it as draft mainly to see if we can avoid new preset but instead add functionality to the main azure-functions (worst case via a runtime flag)


If you like to work and help on v4 support, feel free to open a new PR. Using new compatibility date system we can adopt it progressively (see netlify for reference)

@supersoniko
Copy link
Author

supersoniko commented May 29, 2024

Thanks for working on this dear Sacha. For now i have marked it as draft mainly to see if we can avoid new preset but instead add functionality to the main azure-functions (worst case via a runtime flag)


If you like to work and help on v4 support, feel free to open a new PR. Using new compatibility date system we can adopt it progressively (see netlify for reference)

Thank you for your feedback! I would love to help with v4 support and will get on it this evening. ^^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants