Examples do not reflect real-world use (data fetching is async)

[JakobJingleheimer]

Describe the issue

The docs and examples talk about data being loaded from a database (which would be an asynchronous process), but they actually show data generated synchronously, such as in simple-usage/recipe.resolver where the source data (items) is available statically. In almost any real-world scenario, createRecipeSamples would be async.

Are you able to make a PR that fix this?

Yes, once I have the knowledge.

Additional context

Love the idea of this library!

[MichalLytek]

This is a simple example on purpose. To not bother with data fetching and other boilerplate. Just about the TypeGraphQL syntax and general approach or resolver architecture.

I think you could make a PR with a simple delay helper that resolves a promise after N miliseconds.
Then await it in async resolver, so it's returning the data after like 250ms. WDYT?

[JakobJingleheimer]

This is a simple example on purpose. To not bother with data fetching and other boilerplate. Just about the TypeGraphQL syntax and general approach or resolver architecture.

Mm, but the setup of simple-usage/recipe.resolver is unrealistic, which makes the example a red-herring. Now that I've figured out how to do it, I can update the example 🙂 I think it doesn't need any specific delay, it just needs to be asynchronous (eg async/await or maybe even just Promise.resolve()) in order to sufficiently mimic a real-world scenario.

I'm travelling for the next couple weeks; I'll try to find the time but I'm not sure when it will be.