async createContext for Express Adapter
Been debugging an odd behavior for the past hour, it seems like that an async function does not work in the express adapter. Is that supposed to work or is that the expected behavior? If this is a bug i can toss together a quick sandbox, but figured I check first whether this is expected or not.
If this is expected behavior, should the async calls happen in middleware instead? Seems a bit at odds. Thoughts?
If this is expected behavior, should the async calls happen in middleware instead? Seems a bit at odds. Thoughts?
