You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering if there was any plan to implement the lifespan protocol for the provided asgi server. I think this could be done with extensions or a passing new keyword args to the asgi object. Could be nice for things such as closing DB connections, startup error handling, ect.
The text was updated successfully, but these errors were encountered:
Idea behind default server is to provide people with quick way to get their GraphQL server up and running locally so they can play around - write some schema, run some queries against it to see how resolvers are called, etc. etc.
Obviously this approach is unfit for great majority of "real apps" that will want to do things like manage DB connections and other things you've mentioned. But we really don't want to end up maintaining both the GraphQL server and the ASGI/HTTP stack.
Hi,
I was wondering if there was any plan to implement the lifespan protocol for the provided asgi server. I think this could be done with extensions or a passing new keyword args to the asgi object. Could be nice for things such as closing DB connections, startup error handling, ect.
The text was updated successfully, but these errors were encountered: