[question] How are things like tauri's AppHandle / Window being passed to async_graphql's Context

[mikew]

Note: I would have made this a discussion but it seems like they're not enabled for this repo

I'm using this plugin (still works great btw), but am curious how something like ctx.data::<AppHandle>() is working? ctx is from async_graphql, and AppHandle is something from tauri.

I've been searching through the source code of this plugin, hoping to find an obvious place where you're saying "add tauri's app handle to async_graphql's context", but the only reference to it is in an example in a comment. So, it seems very magical at the moment.

[mikew]

Of course, after posting this I noticed this, which probably answers my question:

tauri-plugin-graphql/src/lib.rs

Line 246 in 78b092d

.execute_batch(req.data(window.app_handle()).data(window))

Now I'm wondering why .inner is needed in subscriptions

tauri-plugin-graphql/src/lib.rs

Line 258 in 78b092d

let mut stream = schema.execute_stream(req.inner.data(window.app_handle()).data(window));