-
Notifications
You must be signed in to change notification settings - Fork 13
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
Support for Azure Functions v4 (?) #41
Comments
Encountering the same issue as well. Seems the package is still using @azure/functions^3.2.0 when it should be using @azure/functions 4.x which changed how function apps are defined in nodejs |
This is related to #42. Azure Functions v4 is a new programming model for JavaScript/TypeScript and it sees quite a few changes to the types that are used, so it's not a direct upgrade. As it's still in public preview I'm holding off supporting Azure Functions v4. |
Makes sense, if you do plan on creating a beta version on a separate branch and are looking for community support I believe some of us on this thread may be interested in helping. |
I did explore it early on (when we were prototyping v4) to see what the approach might look like for building libraries on top of the new programming model. I really wanted to do: import { app } from "@azure/functions";
app.graphql(/* stuff here */); But it's not possible and ended up having some discussion with the Functions team on what could be good options and there's a few to try but... well... time 😅 |
Has any further progress been made on this issue, please? Happy (and eager!) to contribute but want to avoid duplicating anyone else's work. Thanks. |
No I haven't. I've moved out of the JavaScript space at Microsoft so am rather time poor to tackle some of the stuff here. |
No worries, @aaronpowell! I'm happy to start pulling together a PR if you're willing/able to review it? |
More than happy to review |
Thanks! I might take a little while as I have lots of other stuff on my plate right now and I'm only just getting started with Azure Functions, but I'll submit a proof of concept in the next month or so, and we can no doubt all work towards improving it. Appreciate your help. |
@aaronpowell I have fixed the current support of V4 in the current library, Am I allowed to contribute the code?? |
Sure, submit a PR |
Hello everyone, can someone help me set up the repository standard code with the solution? |
@aaronpowell @TengoCharlie is there any progress on this please? here is the article for that release: https://azure.microsoft.com/en-us/updates/generally-available-azure-functions-v4-programming-model-for-nodejs/ |
@douglas-wang , am looking into it. Will raise a PR soon |
I have changes the code as per the function V4. but i have a question that are we going to release another package for function v4 or we will provide support for v4 and v3 by same package? |
It'd be best to support them both in a single package |
@aaronpowell I just opened a PR to address this issue #66 |
Thanks @barddoo, I have tested your PR and works perfectly with Azure functions v4.1.0 and Apollo server v4.10.0 |
@trevor-scheer / @BlenderDude / @michael-watson - This repo has gone stale from an Apollo support standpoint (the last update was 3 months ago) - several people need to update to Azure Functions Programming model v4, and this pull request is blocking them - It looks like @aaronpowell has their attention turned toward other Microsoft priorities, is this something you can help move forward in his absence? (e.g., reviewing and approving the PR) |
As a follow up on this, I just noticed that one cannot access the body in the get context function as one could in V3, as the body can only be parsed once. |
Is there a way to switch to V4 of the Azure Functions? The docs say that you shouldn't have a
function.json
, but it seems that that is necessary to usestartServerAndCreateHandler
?How should you use
startServerAndCreateHandler
in this no-json V4 model?Thanks in advance!
The text was updated successfully, but these errors were encountered: