1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
// Copyright 2023 Tony Mushah
// SPDX-License-Identifier: MIT
//! This crate contains a Tauri plugin builder used to expose a [`async_graphql`]
//! GraphQL endpoint through Tauri's IPC system. This plugin can be used as
//! safer alternative to Tauri's existing Command API since both the Rust and
//! JavaScript side of the interface can be generated from a common schema.
//!
//! ## Rationale
//!
//! Especially in bigger projects that have specialized teams for the Frontend
//! and Rust core the existing command API falls short of being an optimal
//! solution. The Frontend is tightly coupled through `invoke()` calls to
//! backend commands, but there is no type-safety to alert Frontend developers
//! to changes in command signatures. This results in a very brittle interface
//! where changes on the Rust side will inadvertently break code in the
//! Frontend. This problem is similar exiting REST APIs, where the absence of a
//! formal contract between the server and the frontend makes future changes
//! very difficult.
//!
//! We can employ the same techniques used in traditional web development and
//! use shared schema that governs which types, methods, etc. are
//! available. GraphQL is such a schema language.
//!
//! ## Examples
//!
//! For the following examples, it is assumed you are familiar with [`Tauri
//! Commands`][`Commands`], [`Events`] and [`GraphQL`].
//!
//! ### Queries
//!
//! An example app that implements a very simple read-only todo-app using
//! GraphQL:
//!
//! ```rust,no_run
//! use async_graphql::{Schema, EmptySubscription, EmptyMutation, Object, SimpleObject, Result as GraphQLResult};
//!
//! #[derive(SimpleObject, Debug, Clone)]
//! struct ListItem {
//! id: i32,
//! text: String
//! }
//!
//! impl ListItem {
//! pub fn new(text: String) -> Self {
//! Self {
//! id: rand::random::<i32>(),
//! text
//! }
//! }
//! }
//!
//! struct Query;
//!
//! #[Object]
//! impl Query {
//! async fn list(&self) -> GraphQLResult<Vec<ListItem>> {
//! let item = vec![
//! ListItem::new("foo".to_string()),
//! ListItem::new("bar".to_string())
//! ];
//!
//! Ok(item)
//! }
//! }
//!
//! let schema = Schema::new(
//! Query,
//! EmptyMutation,
//! EmptySubscription,
//! );
//!
//! tauri::Builder::default()
//! .plugin(mizuki::Builder::new("todo-plugin", schema).build());
//! ```
//!
//! ### Mutations
//!
//! GraphQL mutations provide a way to update or create state in the Core.
//!
//! Similarly to queries, mutations have access to a context object and can
//! manipulate windows, menus or global state.
//!
//! ```rust,no_run
//! use async_graphql::{Schema, Object, Context, EmptySubscription, EmptyMutation, SimpleObject, Result as GraphQLObject};
//! use tauri::{AppHandle, Manager};
//! use std::sync::Mutex;
//!
//! #[derive(Debug, Default)]
//! struct List(Mutex<Vec<ListItem>>);
//!
//! #[derive(SimpleObject, Debug, Clone)]
//! struct ListItem {
//! id: i32,
//! text: String
//! }
//!
//! impl ListItem {
//! pub fn new(text: String) -> Self {
//! Self {
//! id: rand::random::<i32>(),
//! text
//! }
//! }
//! }
//!
//! struct Query;
//!
//! #[Object]
//! impl Query {
//! async fn list(&self, ctx: &Context<'_>) -> GraphQLObject<Vec<ListItem>> {
//! let app = ctx.data::<AppHandle>().unwrap();
//!
//! let list = app.state::<List>();
//! let list = list.0.lock().unwrap();
//!
//! let items = list.iter().cloned().collect::<Vec<_>>();
//!
//! Ok(items)
//! }
//! }
//!
//! struct Mutation;
//!
//! #[Object]
//! impl Mutation {
//! async fn add_entry(&self, ctx: &Context<'_>, text: String) -> GraphQLObject<ListItem> {
//! let app = ctx.data::<AppHandle>().unwrap();
//!
//! let list = app.state::<List>();
//! let mut list = list.0.lock().unwrap();
//!
//! let item = ListItem::new(text);
//!
//! list.push(item.clone());
//!
//! Ok(item)
//! }
//! }
//!
//! let schema = Schema::new(
//! Query,
//! Mutation,
//! EmptySubscription,
//! );
//!
//! tauri::Builder::default()
//! .plugin(mizuki::Builder::new("list-plugin", schema).build())
//! .setup(|app| {
//! app.manage(List::default());
//!
//! Ok(())
//! });
//! ```
//!
//! ### Subscriptions
//!
//! GraphQL subscriptions are a way to push real-time data to the Frontend.
//! Similarly to queries, a client can request a set of fields, but instead of
//! immediately returning a single answer, a new result is sent to the Frontend
//! every time the Core sends one.
//!
//! Subscription resolvers should be async and must return a [`Stream`].
//!
//! ```rust,no_run
//! use async_graphql::{
//! futures_util::{self, stream::Stream},
//! Schema, Object, Subscription, EmptySubscription,
//! EmptyMutation, SimpleObject, Result as GraphQLResult
//! };
//!
//! struct Query;
//!
//! #[Object]
//! impl Query {
//! async fn hello_world(&self) -> GraphQLResult<&str> {
//! Ok("Hello World!")
//! }
//! }
//!
//! struct Subscription;
//!
//! #[Subscription]
//! impl Subscription {
//! async fn hello_world(&self) -> impl Stream<Item = &str> {
//! futures_util::stream::iter(vec!["Hello", "World!"])
//! }
//! }
//!
//! let schema = Schema::new(
//! Query,
//! EmptyMutation,
//! Subscription,
//! );
//!
//! tauri::Builder::default()
//! .plugin(mizuki::Builder::new("subsciption", schema).build());
//! ```
//!
//! ## Stability
//!
//! To work around limitations with the current command system, this plugin
//! directly implements an invoke handler instead of reyling on the
//! [`tauri::generate_handler`] macro.
//! Since the invoke handler implementation is not considered stable and might
//! change between releases **this plugin builder has no backwards compatibility
//! guarantees**.
//!
//! [`Stream`]: https://docs.rs/futures-util/latest/futures_util/stream/trait.Stream.html
//! [`Commands`]: https://tauri.studio/docs/guides/command
//! [`Events`]: https://tauri.studio/docs/guides/events
//! [`GraphQL`]: https://graphql.org
pub
pub
pub
use Context;
pub use ;
use ;
use CancellationToken;
/// A trait extension
/// to extract [`tauri::AppHandle`], [`tauri::Window`], [`tauri::Webview`]
/// and the subscription [`tokio_util::sync::CancellationToken`]
/// from an [`async_graphql::Context`].