@crowdedkingdoms/crowdyjs 17.14.0-dev.1 → 18.0.1-dev.1

package/dist/errors.js

@@ -169,7 +169,7 @@ export class CrowdyAppUnavailableError extends CrowdyGraphQLError {
  * @example
  * ```ts
  * try {
- *   await client.compute.invoke({ appId, moduleName: 'combat', exportName: 'hit' });
+ *   await client.graphql.request(SomeDocument, variables);
  * } catch (err) {
  *   const fault = playerFaultOf(err);
  *   if (!fault) throw err;
@@ -209,13 +209,10 @@ function faultFields(code, blame, retryable, cause) {
 /**
  * Read the platform's attribution from EITHER carrier, so a game branches once.
  *
- * There are two, and the split is the server's rather than a wart of this SDK.
- * `computeInvoke` and `playerComputeInvoke` FAIL — they throw, and the fault arrives in
- * the GraphQL error's extensions. `gameModelInvoke` RETURNS — a denial or an evaluation
- * failure is a gameplay verdict that still carries an event id and any writes that did
- * apply, so it comes back as `success: false` with a `fault` field. Forcing either into
- * the other's shape would lose something real, so this function accepts both and gives
- * you one thing to switch on.
+ * There are two. A refused or failed call THROWS, and the fault arrives in the GraphQL
+ * error's extensions. A result may instead RETURN one: a verdict that still carries
+ * whatever did apply comes back as `success: false` with a `fault` field. This function
+ * accepts both and gives you one thing to switch on.
  *
  * Returns `null` when there is no fault: a successful result, or an error that is not an
  * attributed one (a network drop, a timeout, an ordinary validation error elsewhere in
@@ -224,8 +221,7 @@ function faultFields(code, blame, retryable, cause) {
  *
  * @example
  * ```ts
- * const result = await client.gameModel.invoke({ appId, functionName, selfContainerId });
- * const fault = playerFaultOf(result);
+ * const fault = playerFaultOf(errorOrResult);
  * if (fault?.retryable) scheduleRetry();
  * ```
  */