@m1212e/rumble 0.18.0 → 0.18.1

package/README.md

@@ -289,6 +289,7 @@ server.listen(3000, () => {
 });
 
 ```
+> If you hit `Query depth limit of N exceeded` (or alias/directive/token limit) errors in production, pass `armorConfig` through to relax the [graphql-armor](https://github.com/Escape-Technologies/graphql-armor) defaults — e.g. `createYoga({ armorConfig: { maxDepth: { n: 20 } } })`. `armorConfig` is forwarded verbatim to `EnvelopArmorPlugin(...)` and is only applied when `enableApiDocs` is `false` (i.e. in production).
 
 ## Usage & client generation
 You can use the GraphQL api with any client you like. However, rumble provides a generation api which can output a TypeScript client from a rumble instance. To perform a generation, use the exported function from your rumble instance like this:
@@ -347,7 +348,6 @@ users.subscribe((s) => s?.at(0));
 console.log(users.firstName)
 ```
 
-> **Error handling**: when the server returns a GraphQL error or a network error occurs, the returned promise rejects with the error. Use `await` (inside try/catch) or `.catch()` to handle it. If you use the fire-and-subscribe pattern (`const r = client.liveQuery.users(…); r.subscribe(…)`) without awaiting, a server error will produce an **unhandled promise rejection** — attach `.catch(() => {})` if you intentionally do not care about the promise result.
 > As of `v0.16.12` the client has special support for the svelte reactive state system (runes). If you run a live query which deploys a subscription inside a svelte effect context, you will get reactivity without subscribing to anything right out of the box. Please see [here](https://github.com/DeutscheModelUnitedNations/munify-chase/blob/f70c4484a92551b564c70603ebfd48d5b8cac637/src/lib/api/customClient.ts#L12) and [here](https://github.com/DeutscheModelUnitedNations/munify-chase/blob/f70c4484a92551b564c70603ebfd48d5b8cac637/src/routes/app/(launcher)/%2Bpage.svelte#L9C9-L9C23) for real world examples.
 ### Alternative decoupled client generation
 As an alternative to use the client generator with a fully instanciated rumble instance, you can also import the `generateFromSchema` function from rumble and pass it a standard `GraphQLSchema` object to generate the client:

package/out/index.cjs

@@ -208,7 +208,7 @@ function mapNullFieldsToUndefined(obj) {
 }
 //#endregion
 //#region package.json
-var version = "0.18.0";
+var version = "0.18.1";
 //#endregion
 //#region lib/helpers/mergeFilters.ts
 function mergeFilters(filterA, filterB) {
@@ -1753,7 +1753,7 @@ export const db = drizzle(
 			context,
 			plugins: [
 				...args?.plugins ?? [],
-				...enableApiDocs ? [] : [(0, _graphql_yoga_plugin_disable_introspection.useDisableIntrospection)(), (0, _escape_tech_graphql_armor.EnvelopArmorPlugin)()],
+				...enableApiDocs ? [] : [(0, _graphql_yoga_plugin_disable_introspection.useDisableIntrospection)(), (0, _escape_tech_graphql_armor.EnvelopArmorPlugin)(args?.armorConfig)],
 				rumbleInput.otel?.enabled ? { onExecute: ({ setExecuteFn, executeFn }) => {
 					setExecuteFn((options) => rumbleInput.otel.tracer.startActiveSpan(_pothos_tracing_opentelemetry.SpanNames.EXECUTE, { attributes: {
 						[_pothos_tracing_opentelemetry.AttributeNames.OPERATION_NAME]: options.operationName ?? "anonymous",