integreat 0.8.9 → 1.0.0-rc.0

package/README.md

@@ -111,8 +111,10 @@ const services = [
     transporter: 'http', // Use the http transporter
     adapters: ['json'], // Run the request and the response through the json adapter
     options: {
-      // Options for the transporter
-      uri: 'https://cat-fact.herokuapp.com/facts', // Only the uri is needed here
+      transporter: {
+        // Options for the transporter
+        uri: 'https://cat-fact.herokuapp.com/facts', // Only the uri is needed here
+      },
     },
     endpoints: [
       {
@@ -204,7 +206,7 @@ for transporters, adapters, etc.
   id: <service id>,
   transporter: <transporter id>,
   adapters: [<adapter id>, <adapter id>, ...],
-  auth: <auth id>,
+  auth: <auth config>,
   meta: <type id>,
   options: {...},
   mutation: <mutation pipeline>,
@@ -226,7 +228,17 @@ The `auth` property should normally be set to the id of an
 [auth definition](#service-authentication), if the service requires
 authentication. In cases where the service is authenticated by other means, e.g.
 by including username and password in the uri, set the `auth` property to `true`
-to signal that this is an authenticated service.
+to signal that this is an authenticated service. For services accepting incoming
+actions, `auth` should be set to an object with
+`{ outgoing: <auth id | true>, incoming: <auth id | true>}`.
+
+**Note:** When connecting to a service for listening, the `outgoing` auth is
+used. `incoming` is only used for validating the actions being dispatched "back"
+from the service.
+
+In `options`, you may provide options for transporters and adapters. It is
+merged with the `options` object on the endpoint. See
+[the `options` object](#options-object) for more on this.
 
 ### Endpoints
 
@@ -278,18 +290,18 @@ Here's the format of an endpoint definition:
     action: <action type>,
     params: {...},
     incoming: <boolean>,
-    filters: {...}
+    conditions: [...]
   },
   validate: [
     {
       condition: <mutation pipeline>,
       failResponse: <response object>
     }
-  ]
-  mutation: <mutation pipeline>,
-  options: {...},
+  ],
+  mutate: <mutation pipeline>,
   allowRawRequest: <boolean>,
   allowRawResponse: <boolean>
+  options: {...},
 }
 ```
 
@@ -305,31 +317,29 @@ specify a few things:
 - `match`: The match object is used to decide the right endpoint for an action.
   More one this in the [Match properties](#match-properties) section.
 - `validate`: This is an array of condition that have to be met in order for
-  Integreat to proceed with the endpoint. This may sound similar to `match`, but
-  `validate` is only processed after a match is found, and if the validation
-  fails, no other endpoint is considered and the `failResponse` is returned as
-  the response from this action without ever running mutations or sending
-  anything to the service (or a `badrequest` response if no `failResponse` is
-  provided). The `condition` is a mutation pipeline that should return a truthy
-  value for the validation to pass. Any falsy value will cause the validation to
-  fail. If `validate` is missing or an empty array, no validation will be done.
-- `mutation`: A mutation pipeline for the endpoint. The pipeline is run for both
+  Integreat to proceed with the endpoint. The `condition` is a mutation pipeline
+  that should return a truthy value for the validation to pass. Any falsy value
+  will cause the validation to fail. If `validate` is missing or an empty array,
+  no validation will be done. This may sound similar to `match`, but `validate`
+  is only processed after a match is found, and if the validation fails, no
+  other endpoint is considered. On a failing validation, the `failResponse` is
+  returned as the response from this action, or a `badrequest` response if no
+  `failResponse` is provided. There's also a shorthand, where you set
+  `failResponse` to a string, which will be the `error` message of the
+  `badrequest` response. The response is passed through the mutation pipeline.
+- `mutate`: A mutation pipeline for the endpoint. The pipeline is run for both
   actions going to a service and the response coming back, so keep this in mind
   when you set up this pipeline. See [Mutation pipelines](#mutations)
-  for more on how to define the mutation.
-- `options`: This object will be passed on to the transporter and may contain
-  any properties that are meaningful to the transporter. You may also add other
-  properties for use in your mutations, but keep in mind that they will be sent
-  to the transporter. The endpoint `options` object is merged with the service
-  `options` object. Endpoint properties will override equally named service
-  properties, but this is done through deep merging, so child objects will be
-  merged as well.
+  for more on how to define the mutation. `mutation` is an alias for `mutate`.
 - `allowRawRequest`: When set to `true`, payload `data` sent to this endpoint
   will not by cast automatically nor will an error be returned if the data is
   not typed.
 - `allowRawResponse`: When set to `true`, response `data` coming from this
   endpoint will not by cast automatically nor will an error be returned if the
   data is not typed.
+- `options`: This object is merged with the `options` object on the service
+  definition, and provide options for transporters and adapters. See
+  [the `options` object](#options-object) for more on this.
 
 #### Match properties
 
@@ -355,10 +365,15 @@ An endpoint may specify none or more of the following match properties:
   case several match, the endpoint with more specified params will be preferred.
 - `incoming`: If this is `true`, it will only match incoming actions, if `false`
   only outgoing, and if not set, it will match both.
-- `filters`: The filter object specifies a set of tests that needs to match an
-  action. The key of the object is a full dot notation path for the action
-  object, e.g. `payload.onlyArchived` and the value is a
-  [JSON Schema Validation object](https://json-schema.org/draft/2020-12/json-schema-validation.html).
+- `conditions`: An array of mutation pipelines that will be run on the action to
+  see if it's a fit for this endpoint. If all pipelines return a truthy value,
+  the endpoint is chosen (given that the other match properties also match). We
+  rely on JavaScript definition of 'truthy' here, so any value that is not
+  `false`, `null`, `undefined`, `0`, `NaN`, or `''` will be considered truthy.
+
+> There used to be a `filters` property on the endpoint match object. It is
+> still supported, but it's deprecated and will be removed in v1.1. Please use
+> `conditions` instead.
 
 > Editor's note: Describe what incoming actions are, and give more details on
 > filters.
@@ -399,7 +414,9 @@ Example service definition with endpoint match object:
         }
       },
       options: {
-        uri: 'https://example.api.com/1.0/{author}/{type}_log?archive={archive}'
+        transporter: {
+          uri: 'https://example.api.com/1.0/{author}/{type}_log?archive={archive}'
+        }
       }
     }
   ],
@@ -407,6 +424,97 @@ Example service definition with endpoint match object:
 }
 ```
 
+### Options object
+
+A service defintion may have `options` object in two places: Direction on the
+service definition and on any of the endpoints. When an action is sent to an
+endpoint, the combination of the two `options` are used. Also, there may be
+different options for the transporter and for the adapters.
+
+Example of an `options` object set on the service definition:
+
+```javascript
+{
+  id: 'entries',
+  options: {
+    uri: 'https://ourapi.com/v1',
+    transporter: {
+      method: 'POST',
+      incoming: { port: 3000 }
+    },
+    adapters: {
+      xml: { namespaces: { ... } },
+      // ...
+    }
+  }
+}
+```
+
+Any properties set directly on the `options` object or on a `transporter`
+property, are treated as options for the transporter. If there are properties on
+both the `options` and a `transporter` object, they will be merged, with the
+`transporter` object having priority if conflicts. This is a shallow merge, so
+objects used in the options will not be merged.
+
+In the example above, the options passed to the transporter will include `uri`,
+`method`, and `incoming`.
+
+The `incoming` object on the transporter options is a bit special, as it holds
+separate options for transporters that support incoming requests trough the
+`listen()` method. If there are `incoming` objects on both the `options` and
+`transporter` objects, they will be merged, again with priority to the one on
+the `transporter` object.
+
+Note that we recommend setting transporter options on the `transporter` object
+for clarity, but both will work.
+
+Adapter options may be given in an `adapters` object, where each adapter may
+have its own options, set with the id of the adapter as a key. In the example
+above, the `xml` adapter will be given the `namespaces` object. A requirement
+for this, is that the adapter actually have an id. Adapters provided directly on
+service definition may not have an id, but all adapters that are referenced by
+an id, will also be given options set on that id, which is the common behavior.
+
+Finally, when all this sorting have been done on options from both the service
+definition and an endpoint, the two options structures are merged before being
+used. Here, the endpoint options take priority, so that you may set a general
+option on the service, and override it on the endpoint.
+
+Example of endpoint options overriding service options:
+
+```javascript
+{
+  id: 'entries',
+  options: {
+    transporter: {
+      uri: 'https://ourapi.com/v1',
+      method: 'GET',
+    }
+  },
+  endpoints: [
+    {
+      match: { ... }
+    },
+    {
+      match: { ... },
+      options: {
+        transporter: {
+          method: 'POST'
+        }
+      }
+    }
+  ]
+}
+```
+
+Here, the first enpoint will be given `method: 'GET'`, while the next will get
+`method: 'POST'`.
+
+Before actions are passed through mutations and finally passed to the
+transporter, the merged transporter options is set on an `options` property in
+the `meta` object of the action. This way, you may also mutate these options
+before they reach the transporter.
+
 ### Service authentication
 
 This definition format is used to authenticate with a service:
@@ -431,6 +539,8 @@ This definition format is used to authenticate with a service:
 
 Available authenticators:
 
+- `anonymous`: Will always grant access and return an ident with id
+  `'anonymous'` on validation. This is built into Integreat.
 - `options`: Will pass on the options as authentication, so whatever you provide
   here is the authentication. What options to provide, then, is depending on
   what the relevant transporter requires. This is built into Integreat.
@@ -810,7 +920,7 @@ Set the `access` property on a schema to enforce permission checking. This
 applies to any service that provides data in this schema.
 
 The simplest access rule is `auth`, which means that anyone can do anything with
-the data of this schema, as long as they are authenticated. Being authenticated
+the data of this schema, as long as they are authenticated. Being authenticated,
 in this context, means that the dispatched action has an `ident` in the `meta`
 object. See [the section on idents](#idents) for more on this.
 
@@ -1084,7 +1194,8 @@ Current meta properties reserved by Integreat:
   Integreat).
 - `options`: Used for passing the processed service endpoint options object to
   a transporter. The `options` object is available through mutations, so that
-  you may modify it futher before it goes to the transporter.
+  you may modify it futher before it goes to the transporter. Note that only the
+  transporter options are provided here, not the adapter options.
 - `authorized`: An internal flag signaling that the action has been authorized.
   Will be removed from any dispatched actions.
 
@@ -1098,12 +1209,12 @@ When you dispatch an action, you will get a response object back in this format:
   data: <data from the service, usually mutated>,
   error: <error message>,
   warning: <warning message>,
-  access: <ident of the user>,
+  origin: <code telling where an error originated>
+  access: <holds the ident actually being used>,
   paging: <pagination objects>,
   params: <key/value pairs>,
   headers: <key/value pairs>,
   responses: <array of sub-responses when relevant>,
-  meta: <meta object>
 }
 ```
 
@@ -1120,6 +1231,13 @@ When you dispatch an action, you will get a response object back in this format:
   should know, the warning message is where you'll get noticed. An example is
   when you get an array of data items, but some of them was removed due to the
   access of the ident on the action.
+- `origin`: When the response is an error (status is not `'ok'` or `'queue'`),
+  this property will hold a code for where the error originated. The goal is to
+  set it as close to the actual origin as possible. See
+  [list of origin codes](#origin-codes) below.
+- `access`: An object holding the `ident` that was actually being used. This may
+  be different than the `meta.ident` on the action, as the ident may also be
+  mutated or completed with roles etc. along the way.
 - `paging`: For services and transporters that support
   [pagination](#pagination), this object will hold information about how to get
   the next or previous page, in a `next` or `prev` object. These objects are
@@ -1136,8 +1254,6 @@ When you dispatch an action, you will get a response object back in this format:
   `SYNC` or `RUN`. The action handlers _may_ then provide an array of all the
   sub-response objects here.
 
-> Editor's note: Do we return access in responses?
-> Editor's note: Do we return meta in responses?
 > Editor's note: Is it correct that queues return the id in the data?
 
 When the status is `queued`, the id of the queued action may found in
@@ -1146,7 +1262,8 @@ the same as `action.meta.id`.
 
 ### Status codes
 
-The `status` or the action response will be one of the following status codes:
+The `status` property on the action response will be one of the following status
+codes:
 
 - `ok`: Everything is well, data is returned as expected
 - `queued`: The action has been queued. This is regarded as a success status
@@ -1160,6 +1277,37 @@ The `status` or the action response will be one of the following status codes:
 - `badresponse`: Response data is not as expected
 - `error`: Any other error
 
+### Origin codes
+
+The `origin` property is not exclusively defined, but these are some of the more
+common codes:
+
+- `service:<service id>`: The error originated in service. There may also be
+  third level of detail here, if the service sets an origin code of its own.
+  E.g. `'service:entries:handshake`.
+- `middleware:service:<service id>`: The error happened in the middleware chain
+  on the service side.
+- `internal:service:<service id>`: Used for errors in the service class, that
+  has nothing to do with the actual service, e.g. if the service class is not
+  configured correctly.
+- `mutate:request`: The error was set in a request mutation pipeline.
+- `mutate:response`: The error was set in a response mutation pipeline.
+- `auth:action`: The error occured while attempting to authorize the action.
+- `auth:data`: The error occured while attempting to authorize data in an
+  action payload or a response.
+- `auth:service:<service id>`: The error occured while attempting to authorize
+  the service with the given id.
+- `auth:service:<service id>:<authenticator id>`: The error occured while
+  attempting to authorize the service with the given id, through the given
+  authenticator.
+- `handler:<handler id>`: The error occurred with the handler with the given id,
+  e.g. `'handler:GET'`. This means the error did happen in the service or the
+  mutation pipelines, but in the internal workings of then handler.
+- `middleware:dispatch`: The error happened within the middleware chain, on the
+  `dispatch()` end (not on the service end).
+- `dispatch`: This is the lowest level of origin, as the error happened within
+  the `dispatch()` method.
+
 ### Idents
 
 An ident in Integreat is basically an id unique to one participant in the

package/dist/authenticators/anonymous.d.ts

@@ -0,0 +1,3 @@
+import type { Authenticator } from '../types.js';
+declare const anonymousAuth: Authenticator;
+export default anonymousAuth;

package/dist/authenticators/anonymous.js

@@ -0,0 +1,22 @@
+const anonymousAuth = {
+    id: 'anonymous',
+    async authenticate(_options) {
+        return { status: 'granted' };
+    },
+    isAuthenticated(_authentication) {
+        return true;
+    },
+    async validate(_authentication) {
+        return { id: 'anonymous' };
+    },
+    authentication: {
+        asObject(_authentication) {
+            return {};
+        },
+        asHttpHeaders(_authentication) {
+            return {};
+        },
+    },
+};
+export default anonymousAuth;
+//# sourceMappingURL=anonymous.js.map

package/dist/authenticators/anonymous.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"anonymous.js","sourceRoot":"","sources":["../../src/authenticators/anonymous.ts"],"names":[],"mappings":"AAKA,MAAM,aAAa,GAAkB;IACnC,EAAE,EAAE,WAAW;IAOf,KAAK,CAAC,YAAY,CAAC,QAAQ;QACzB,OAAO,EAAE,MAAM,EAAE,SAAS,EAAE,CAAA;IAC9B,CAAC;IAMD,eAAe,CAAC,eAAe;QAC7B,OAAO,IAAI,CAAA;IACb,CAAC;IAMD,KAAK,CAAC,QAAQ,CAAC,eAAe;QAC5B,OAAO,EAAE,EAAE,EAAE,WAAW,EAAE,CAAA;IAC5B,CAAC;IAED,cAAc,EAAE;QAMd,QAAQ,CAAC,eAAe;YACtB,OAAO,EAAE,CAAA;QACX,CAAC;QAOD,aAAa,CAAC,eAAe;YAC3B,OAAO,EAAE,CAAA;QACX,CAAC;KACF;CACF,CAAA;AAED,eAAe,aAAa,CAAA"}

package/dist/authenticators/index.d.ts

@@ -1,2 +1,3 @@
+export { default as anonymous } from './anonymous.js';
 export { default as options } from './options.js';
 export { default as token } from './token.js';

package/dist/authenticators/index.js

@@ -1,3 +1,4 @@
+export { default as anonymous } from './anonymous.js';
 export { default as options } from './options.js';
 export { default as token } from './token.js';
 //# sourceMappingURL=index.js.map

package/dist/authenticators/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/authenticators/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,OAAO,IAAI,OAAO,EAAE,MAAM,cAAc,CAAA;AACjD,OAAO,EAAE,OAAO,IAAI,KAAK,EAAE,MAAM,YAAY,CAAA"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/authenticators/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,OAAO,IAAI,SAAS,EAAE,MAAM,gBAAgB,CAAA;AACrD,OAAO,EAAE,OAAO,IAAI,OAAO,EAAE,MAAM,cAAc,CAAA;AACjD,OAAO,EAAE,OAAO,IAAI,KAAK,EAAE,MAAM,YAAY,CAAA"}

package/dist/authenticators/options.d.ts

@@ -1,3 +1,3 @@
-import type { Authenticator } from '../service/types.js';
+import type { Authenticator } from '../types.js';
 declare const optionsAuth: Authenticator;
 export default optionsAuth;

package/dist/authenticators/options.js

@@ -1,9 +1,9 @@
 import { isObject } from '../utils/is.js';
 const optionsAuth = {
-    async authenticate(options, _action) {
+    async authenticate(options) {
         return { status: 'granted', ...options };
     },
-    isAuthenticated(authentication, _options, _action) {
+    isAuthenticated(authentication) {
         return !!(authentication && authentication.status === 'granted');
     },
     authentication: {

package/dist/authenticators/options.js.map

@@ -1 +1 @@
-{"version":3,"file":"options.js","sourceRoot":"","sources":["../../src/authenticators/options.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,QAAQ,EAAE,MAAM,gBAAgB,CAAA;AAMzC,MAAM,WAAW,GAAkB;IAQjC,KAAK,CAAC,YAAY,CAAC,OAAO,EAAE,OAAO;QACjC,OAAO,EAAE,MAAM,EAAE,SAAS,EAAE,GAAG,OAAO,EAAE,CAAA;IAC1C,CAAC;IAOD,eAAe,CAAC,cAAc,EAAE,QAAQ,EAAE,OAAO;QAC/C,OAAO,CAAC,CAAC,CAAC,cAAc,IAAI,cAAc,CAAC,MAAM,KAAK,SAAS,CAAC,CAAA;IAClE,CAAC;IAED,cAAc,EAAE;QAOd,QAAQ,CAAC,cAAqC;YAC5C,IAAI,QAAQ,CAAC,cAAc,CAAC,EAAE;gBAC5B,MAAM,EAAE,MAAM,EAAE,GAAG,OAAO,EAAE,GAAG,cAAc,CAAA;gBAC7C,IAAI,MAAM,KAAK,SAAS,EAAE;oBACxB,OAAO,OAAO,CAAA;iBACf;aACF;YACD,OAAO,EAAE,CAAA;QACX,CAAC;QAOD,aAAa,CACX,cAAqC;YAErC,IAAI,QAAQ,CAAC,cAAc,CAAC,EAAE;gBAC5B,MAAM,EAAE,MAAM,EAAE,GAAG,OAAO,EAAE,GAAG,cAAc,CAAA;gBAC7C,IAAI,MAAM,KAAK,SAAS,EAAE;oBACxB,OAAO,OAAO,CAAA;iBACf;aACF;YACD,OAAO,EAAE,CAAA;QACX,CAAC;KACF;CACF,CAAA;AAED,eAAe,WAAW,CAAA"}
+{"version":3,"file":"options.js","sourceRoot":"","sources":["../../src/authenticators/options.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,QAAQ,EAAE,MAAM,gBAAgB,CAAA;AAQzC,MAAM,WAAW,GAAkB;IAQjC,KAAK,CAAC,YAAY,CAAC,OAAO;QACxB,OAAO,EAAE,MAAM,EAAE,SAAS,EAAE,GAAG,OAAO,EAAE,CAAA;IAC1C,CAAC;IAOD,eAAe,CAAC,cAAc;QAC5B,OAAO,CAAC,CAAC,CAAC,cAAc,IAAI,cAAc,CAAC,MAAM,KAAK,SAAS,CAAC,CAAA;IAClE,CAAC;IAED,cAAc,EAAE;QAOd,QAAQ,CAAC,cAAqC;YAC5C,IAAI,QAAQ,CAAC,cAAc,CAAC,EAAE;gBAC5B,MAAM,EAAE,MAAM,EAAE,GAAG,OAAO,EAAE,GAAG,cAAc,CAAA;gBAC7C,IAAI,MAAM,KAAK,SAAS,EAAE;oBACxB,OAAO,OAAO,CAAA;iBACf;aACF;YACD,OAAO,EAAE,CAAA;QACX,CAAC;QAOD,aAAa,CACX,cAAqC;YAErC,IAAI,QAAQ,CAAC,cAAc,CAAC,EAAE;gBAC5B,MAAM,EAAE,MAAM,EAAE,GAAG,OAAO,EAAE,GAAG,cAAc,CAAA;gBAC7C,IAAI,MAAM,KAAK,SAAS,EAAE;oBACxB,OAAO,OAAO,CAAA;iBACf;aACF;YACD,OAAO,EAAE,CAAA;QACX,CAAC;KACF;CACF,CAAA;AAED,eAAe,WAAW,CAAA"}

package/dist/authenticators/token.d.ts

@@ -1,4 +1,4 @@
-import type { Authenticator } from '../service/types.js';
+import type { Authenticator } from '../types.js';
 export interface TokenObject extends Record<string, unknown> {
     token?: string | null;
     type?: string;

package/dist/authenticators/token.js

@@ -9,13 +9,13 @@ const getTypeAndToken = (authentication) => {
     };
 };
 const tokenAuth = {
-    async authenticate(options, _action) {
+    async authenticate(options) {
         const { token = null, type, encode = false } = options || {};
         return token
             ? { status: 'granted', token, type, encode }
             : { status: 'refused' };
     },
-    isAuthenticated(authentication, _options, _action) {
+    isAuthenticated(authentication) {
         return !!(authentication &&
             authentication.status === 'granted' &&
             authentication.token);

package/dist/authenticators/token.js.map

@@ -1 +1 @@
-{"version":3,"file":"token.js","sourceRoot":"","sources":["../../src/authenticators/token.ts"],"names":[],"mappings":"AAiBA,MAAM,eAAe,GAAG,CAAC,cAA0C,EAAE,EAAE;IACrE,MAAM,EAAE,MAAM,EAAE,KAAK,EAAE,IAAI,EAAE,MAAM,EAAE,GAAG,cAAc,IAAI,EAAE,CAAA;IAC5D,IAAI,MAAM,KAAK,SAAS,IAAI,CAAC,KAAK,EAAE;QAClC,OAAO,EAAE,CAAA;KACV;IACD,OAAO;QACL,KAAK,EAAE,MAAM,CAAC,CAAC,CAAC,MAAM,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,QAAQ,CAAC,QAAQ,CAAC,CAAC,CAAC,CAAC,KAAK;QAC7D,IAAI;KACL,CAAA;AACH,CAAC,CAAA;AAKD,MAAM,SAAS,GAAkB;IAO/B,KAAK,CAAC,YAAY,CAAC,OAAO,EAAE,OAAO;QACjC,MAAM,EAAE,KAAK,GAAG,IAAI,EAAE,IAAI,EAAE,MAAM,GAAG,KAAK,EAAE,GAAG,OAAO,IAAI,EAAE,CAAA;QAC5D,OAAO,KAAK;YACV,CAAC,CAAC,EAAE,MAAM,EAAE,SAAS,EAAE,KAAK,EAAE,IAAI,EAAE,MAAM,EAAE;YAC5C,CAAC,CAAC,EAAE,MAAM,EAAE,SAAS,EAAE,CAAA;IAC3B,CAAC;IAOD,eAAe,CAAC,cAAc,EAAE,QAAQ,EAAE,OAAO;QAC/C,OAAO,CAAC,CAAC,CACP,cAAc;YACd,cAAc,CAAC,MAAM,KAAK,SAAS;YACnC,cAAc,CAAC,KAAK,CACrB,CAAA;IACH,CAAC;IAED,cAAc,EAAE;QAOd,QAAQ,CAAC,cAA0C;YACjD,OAAO,eAAe,CAAC,cAAc,CAAC,CAAA;QACxC,CAAC;QAQD,aAAa,CAAC,cAA0C;YACtD,MAAM,EAAE,IAAI,EAAE,KAAK,EAAE,GAAG,eAAe,CAAC,cAAc,CAAC,CAAA;YACvD,OAAO,KAAK,CAAC,CAAC,CAAC,EAAE,aAAa,EAAE,IAAI,CAAC,CAAC,CAAC,GAAG,IAAI,IAAI,KAAK,EAAE,CAAC,CAAC,CAAC,KAAK,EAAE,CAAC,CAAC,CAAC,EAAE,CAAA;QAC1E,CAAC;KACF;CACF,CAAA;AAED,eAAe,SAAS,CAAA"}
+{"version":3,"file":"token.js","sourceRoot":"","sources":["../../src/authenticators/token.ts"],"names":[],"mappings":"AAkBA,MAAM,eAAe,GAAG,CAAC,cAA0C,EAAE,EAAE;IACrE,MAAM,EAAE,MAAM,EAAE,KAAK,EAAE,IAAI,EAAE,MAAM,EAAE,GAAG,cAAc,IAAI,EAAE,CAAA;IAC5D,IAAI,MAAM,KAAK,SAAS,IAAI,CAAC,KAAK,EAAE;QAClC,OAAO,EAAE,CAAA;KACV;IACD,OAAO;QACL,KAAK,EAAE,MAAM,CAAC,CAAC,CAAC,MAAM,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,QAAQ,CAAC,QAAQ,CAAC,CAAC,CAAC,CAAC,KAAK;QAC7D,IAAI;KACL,CAAA;AACH,CAAC,CAAA;AAKD,MAAM,SAAS,GAAkB;IAO/B,KAAK,CAAC,YAAY,CAAC,OAAO;QACxB,MAAM,EAAE,KAAK,GAAG,IAAI,EAAE,IAAI,EAAE,MAAM,GAAG,KAAK,EAAE,GAAG,OAAO,IAAI,EAAE,CAAA;QAC5D,OAAO,KAAK;YACV,CAAC,CAAC,EAAE,MAAM,EAAE,SAAS,EAAE,KAAK,EAAE,IAAI,EAAE,MAAM,EAAE;YAC5C,CAAC,CAAC,EAAE,MAAM,EAAE,SAAS,EAAE,CAAA;IAC3B,CAAC;IAOD,eAAe,CAAC,cAAc;QAC5B,OAAO,CAAC,CAAC,CACP,cAAc;YACd,cAAc,CAAC,MAAM,KAAK,SAAS;YACnC,cAAc,CAAC,KAAK,CACrB,CAAA;IACH,CAAC;IAED,cAAc,EAAE;QAOd,QAAQ,CAAC,cAA0C;YACjD,OAAO,eAAe,CAAC,cAAc,CAAC,CAAA;QACxC,CAAC;QAQD,aAAa,CAAC,cAA0C;YACtD,MAAM,EAAE,IAAI,EAAE,KAAK,EAAE,GAAG,eAAe,CAAC,cAAc,CAAC,CAAA;YACvD,OAAO,KAAK,CAAC,CAAC,CAAC,EAAE,aAAa,EAAE,IAAI,CAAC,CAAC,CAAC,GAAG,IAAI,IAAI,KAAK,EAAE,CAAC,CAAC,CAAC,KAAK,EAAE,CAAC,CAAC,CAAC,EAAE,CAAA;QAC1E,CAAC;KACF;CACF,CAAA;AAED,eAAe,SAAS,CAAA"}

package/dist/close.d.ts

@@ -1,3 +1,3 @@
-import type { Service } from './service/types.js';
+import type Service from './service/Service.js';
 import type { Response } from './types.js';
 export default function close(services: Service[]): Promise<Response>;

package/dist/dispatch.d.ts

@@ -1,12 +1,12 @@
 import type { Dispatch, Middleware, ActionHandler, HandlerOptions } from './types.js';
-import type { Service } from './service/types.js';
-import type { Schema } from './schema/index.js';
-export declare const compose: (...fns: Middleware[]) => Middleware;
+import type Service from './service/Service.js';
+import type Schema from './schema/Schema.js';
 export interface Resources {
     handlers: Record<string, ActionHandler>;
-    schemas: Record<string, Schema>;
+    schemas: Map<string, Schema>;
     services: Record<string, Service>;
     middleware?: Middleware[];
     options: HandlerOptions;
 }
+export declare const compose: (...fns: Middleware[]) => Middleware;
 export default function createDispatch({ handlers, schemas, services, middleware, options, }: Resources): Dispatch;