@qti-components/base 2.5.0 → 3.0.0-next.4

package/dist/context/config.context.d.ts

@@ -77,8 +77,9 @@ export interface ConfigContext {
      */
     inlineChoicePrompt?: string;
     /**
-     * If true, the inline choice interaction automatically measures the widest option and sizes the
-     * trigger button to match. Defaults to false.
+     * The inline choice interaction measures the widest option and sizes the trigger to match, so
+     * choosing an option never changes the field's width. Defaults to true; set false to size the
+     * field to the option shown.
      * When a `qti-input-width-*` class is present on the interaction, that class width always takes
      * precedence and autosizing is skipped regardless of this setting.
      */

package/dist/context/config.context.js.map

@@ -1 +1 @@
-{"version":3,"file":"config.context.js","sourceRoot":"","sources":["../../src/context/config.context.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,aAAa,EAAE,MAAM,cAAc,CAAC;AAiG7C,MAAM,CAAC,MAAM,aAAa,GAAG,aAAa,CAA0B,MAAM,CAAC,eAAe,CAAC,CAAC,CAAC","sourcesContent":["import { createContext } from '@lit/context';\n\nexport type ValidationDisplayMode = 'inline' | 'native' | 'both' | 'none';\n\n/**\n * Configuration context for QTI components. Provides runtime options for assessment item and\n * interaction behavior.\n *\n * ── Three ways to set it, in the order you should reach for them ─────────────────────────────\n *\n * 1. **On a provider**, for real delivery. `qti-test` and `qti-item` both provide it, so setting\n *    `item.configContext = {…}` configures every interaction inside.\n *\n * 2. **On one interaction, directly** — the development-time route, and the reason\n *    `Interaction.configContext` is public:\n *\n *        orderInteraction.configContext = { allowReorder: false };\n *\n *    or, in a lit-html template, as a property binding — which lands before `connectedCallback`:\n *\n *        html`<qti-order-interaction .configContext=${{ allowReorder: false }}>…`\n *\n *    An interaction has to work standalone, so in a story or a spec there is usually no provider\n *    above it, and then nothing ever overwrites what you set. Where a provider DOES exist it wins on\n *    its next emit, because `@consume` writes that same field.\n *\n *    A `qti-config-test-provider` element used to exist for scoping config to a subtree. It is gone:\n *    it was test-only yet registered itself into every consumer's element registry via an unguarded\n *    `@customElement`, which threw whenever two copies of this package ended up in one module graph.\n *    Bind the property on each interaction instead, or provide from `qti-item`.\n *\n * There is no merging at any level: @lit/context resolves to the nearest provider and that object\n * replaces the ancestor's wholesale. A deeper provider therefore has to restate anything from above\n * that it still wants.\n *\n * Note what is NOT here. Options an item author chooses per question are attributes on the\n * interaction (`auto-size-dropzones`, `max-associations`, `disable-animations`); options only a\n * developer chooses are mixin factory arguments or method overrides. This context is for what a\n * delivery environment decides across items. `interactionContext` and `dragDropContext` are neither\n * — they publish derived state (what a choice IS, what a drop HOLDS), never configuration.\n */\nexport interface ConfigContext {\n  /**\n   * Optional category label for info items, used for reporting or display purposes.\n   * Example: \"General Information\", \"Instructions\".\n   */\n  infoItemCategory?: string;\n\n  /**\n   * If true, calls reportValidity() on interactions after scoring to show validation feedback.\n   * Used to trigger UI validation after a scoring event.\n   */\n  reportValidityAfterScoring?: boolean;\n\n  /**\n   * Controls how validation feedback is displayed by interactions:\n   * - 'inline': render message in #validation-message (default behavior)\n   * - 'native': use browser-native reportValidity popup behavior\n   * - 'both': show both inline and native feedback\n   * - 'none': keep validity state only, without visual feedback\n   */\n  validationDisplayMode?: ValidationDisplayMode;\n\n  /**\n   * If true, disables further user actions when an interaction reaches its configured maximum.\n   * Applies to both choice-based and drag/drop interactions.\n   */\n  disableAfterMaxReached?: boolean;\n\n  /**\n   * If false, chips already placed in a drop target cannot be reordered or moved between targets in\n   * drag/drop sortable interactions (order, match, gap-match). Defaults to true. A per-interaction\n   * `allowReorder` property overrides this.\n   */\n  allowReorder?: boolean;\n\n  /**\n   * If true, disables further selection in choice interactions after the maximum number of choices is reached.\n   * @deprecated Legacy alias for choice interactions. Prefer disableAfterMaxReached.\n   */\n  disableAfterIfMaxChoicesReached?: boolean;\n\n  /**\n   * Optional prompt text to display in inline choice interactions when no option is selected.\n   * Example: \"Select an answer...\"\n   */\n  inlineChoicePrompt?: string;\n\n  /**\n   * If true, the inline choice interaction automatically measures the widest option and sizes the\n   * trigger button to match. Defaults to false.\n   * When a `qti-input-width-*` class is present on the interaction, that class width always takes\n   * precedence and autosizing is skipped regardless of this setting.\n   */\n  inlineChoiceAutosize?: boolean;\n}\n\nexport const configContext = createContext<Readonly<ConfigContext>>(Symbol('configContext'));\n"]}
+{"version":3,"file":"config.context.js","sourceRoot":"","sources":["../../src/context/config.context.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,aAAa,EAAE,MAAM,cAAc,CAAC;AAkG7C,MAAM,CAAC,MAAM,aAAa,GAAG,aAAa,CAA0B,MAAM,CAAC,eAAe,CAAC,CAAC,CAAC","sourcesContent":["import { createContext } from '@lit/context';\n\nexport type ValidationDisplayMode = 'inline' | 'native' | 'both' | 'none';\n\n/**\n * Configuration context for QTI components. Provides runtime options for assessment item and\n * interaction behavior.\n *\n * ── Three ways to set it, in the order you should reach for them ─────────────────────────────\n *\n * 1. **On a provider**, for real delivery. `qti-test` and `qti-item` both provide it, so setting\n *    `item.configContext = {…}` configures every interaction inside.\n *\n * 2. **On one interaction, directly** — the development-time route, and the reason\n *    `Interaction.configContext` is public:\n *\n *        orderInteraction.configContext = { allowReorder: false };\n *\n *    or, in a lit-html template, as a property binding — which lands before `connectedCallback`:\n *\n *        html`<qti-order-interaction .configContext=${{ allowReorder: false }}>…`\n *\n *    An interaction has to work standalone, so in a story or a spec there is usually no provider\n *    above it, and then nothing ever overwrites what you set. Where a provider DOES exist it wins on\n *    its next emit, because `@consume` writes that same field.\n *\n *    A `qti-config-test-provider` element used to exist for scoping config to a subtree. It is gone:\n *    it was test-only yet registered itself into every consumer's element registry via an unguarded\n *    `@customElement`, which threw whenever two copies of this package ended up in one module graph.\n *    Bind the property on each interaction instead, or provide from `qti-item`.\n *\n * There is no merging at any level: @lit/context resolves to the nearest provider and that object\n * replaces the ancestor's wholesale. A deeper provider therefore has to restate anything from above\n * that it still wants.\n *\n * Note what is NOT here. Options an item author chooses per question are attributes on the\n * interaction (`auto-size-dropzones`, `max-associations`, `disable-animations`); options only a\n * developer chooses are mixin factory arguments or method overrides. This context is for what a\n * delivery environment decides across items. `interactionContext` and `dragDropContext` are neither\n * — they publish derived state (what a choice IS, what a drop HOLDS), never configuration.\n */\nexport interface ConfigContext {\n  /**\n   * Optional category label for info items, used for reporting or display purposes.\n   * Example: \"General Information\", \"Instructions\".\n   */\n  infoItemCategory?: string;\n\n  /**\n   * If true, calls reportValidity() on interactions after scoring to show validation feedback.\n   * Used to trigger UI validation after a scoring event.\n   */\n  reportValidityAfterScoring?: boolean;\n\n  /**\n   * Controls how validation feedback is displayed by interactions:\n   * - 'inline': render message in #validation-message (default behavior)\n   * - 'native': use browser-native reportValidity popup behavior\n   * - 'both': show both inline and native feedback\n   * - 'none': keep validity state only, without visual feedback\n   */\n  validationDisplayMode?: ValidationDisplayMode;\n\n  /**\n   * If true, disables further user actions when an interaction reaches its configured maximum.\n   * Applies to both choice-based and drag/drop interactions.\n   */\n  disableAfterMaxReached?: boolean;\n\n  /**\n   * If false, chips already placed in a drop target cannot be reordered or moved between targets in\n   * drag/drop sortable interactions (order, match, gap-match). Defaults to true. A per-interaction\n   * `allowReorder` property overrides this.\n   */\n  allowReorder?: boolean;\n\n  /**\n   * If true, disables further selection in choice interactions after the maximum number of choices is reached.\n   * @deprecated Legacy alias for choice interactions. Prefer disableAfterMaxReached.\n   */\n  disableAfterIfMaxChoicesReached?: boolean;\n\n  /**\n   * Optional prompt text to display in inline choice interactions when no option is selected.\n   * Example: \"Select an answer...\"\n   */\n  inlineChoicePrompt?: string;\n\n  /**\n   * The inline choice interaction measures the widest option and sizes the trigger to match, so\n   * choosing an option never changes the field's width. Defaults to true; set false to size the\n   * field to the option shown.\n   * When a `qti-input-width-*` class is present on the interaction, that class width always takes\n   * precedence and autosizing is skipped regardless of this setting.\n   */\n  inlineChoiceAutosize?: boolean;\n}\n\nexport const configContext = createContext<Readonly<ConfigContext>>(Symbol('configContext'));\n"]}

package/dist/context/session.context.d.ts

@@ -8,6 +8,12 @@ export interface SessionContext {
     /** @deprecated Never set by the library. Removed in the next major. */
     navTestLoading?: boolean;
     view?: View;
+    /**
+     * What test plugins keep, by plugin name: JSON the test stores and restores without reading it.
+     * Part of the persisted state (`QtiTestState.session.plugins`); written through the
+     * `cito-test-update-plugin-state` request.
+     */
+    plugins?: Readonly<Record<string, unknown>>;
 }
 export declare const INITIAL_SESSION_CONTEXT: Readonly<SessionContext>;
 export declare const sessionContext: {

package/dist/context/session.context.js.map

@@ -1 +1 @@
-{"version":3,"file":"session.context.js","sourceRoot":"","sources":["../../src/context/session.context.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,aAAa,EAAE,MAAM,cAAc,CAAC;AAe7C,MAAM,CAAC,MAAM,uBAAuB,GAA6B,EAAE,IAAI,EAAE,WAAW,EAAE,CAAC;AAEvF,MAAM,CAAC,MAAM,cAAc,GAAG,aAAa,CAA2B,MAAM,CAAC,gBAAgB,CAAC,CAAC,CAAC","sourcesContent":["import { createContext } from '@lit/context';\n\nexport type View = 'author' | 'candidate' | 'proctor' | 'scorer' | 'testConstructor' | 'tutor' | '';\n\nexport interface SessionContext {\n  navPartId?: string | null;\n  navSectionId?: string | null;\n  navItemRefId?: string | null;\n  /** @deprecated Never set by the library. Removed in the next major. */\n  navItemLoading?: boolean;\n  /** @deprecated Never set by the library. Removed in the next major. */\n  navTestLoading?: boolean;\n  view?: View;\n}\n\nexport const INITIAL_SESSION_CONTEXT: Readonly<SessionContext> = { view: 'candidate' };\n\nexport const sessionContext = createContext<Readonly<SessionContext>>(Symbol('sessionContext'));\n"]}
+{"version":3,"file":"session.context.js","sourceRoot":"","sources":["../../src/context/session.context.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,aAAa,EAAE,MAAM,cAAc,CAAC;AAqB7C,MAAM,CAAC,MAAM,uBAAuB,GAA6B,EAAE,IAAI,EAAE,WAAW,EAAE,CAAC;AAEvF,MAAM,CAAC,MAAM,cAAc,GAAG,aAAa,CAA2B,MAAM,CAAC,gBAAgB,CAAC,CAAC,CAAC","sourcesContent":["import { createContext } from '@lit/context';\n\nexport type View = 'author' | 'candidate' | 'proctor' | 'scorer' | 'testConstructor' | 'tutor' | '';\n\nexport interface SessionContext {\n  navPartId?: string | null;\n  navSectionId?: string | null;\n  navItemRefId?: string | null;\n  /** @deprecated Never set by the library. Removed in the next major. */\n  navItemLoading?: boolean;\n  /** @deprecated Never set by the library. Removed in the next major. */\n  navTestLoading?: boolean;\n  view?: View;\n  /**\n   * What test plugins keep, by plugin name: JSON the test stores and restores without reading it.\n   * Part of the persisted state (`QtiTestState.session.plugins`); written through the\n   * `cito-test-update-plugin-state` request.\n   */\n  plugins?: Readonly<Record<string, unknown>>;\n}\n\nexport const INITIAL_SESSION_CONTEXT: Readonly<SessionContext> = { view: 'candidate' };\n\nexport const sessionContext = createContext<Readonly<SessionContext>>(Symbol('sessionContext'));\n"]}

package/dist/context/types/computed.types.d.ts

@@ -18,6 +18,8 @@ export type ComputedItem = ComputedItemContext & {
 };
 export type ComputedContext = {
     view: View;
+    /** What test plugins keep, by plugin name (`QtiTestState.session.plugins`). Read-only; write with `cito-test-update-plugin-state`. */
+    plugins?: Readonly<Record<string, unknown>>;
     identifier: string;
     title: string;
     testParts: {
@@ -37,4 +39,11 @@ export type ComputedContext = {
             allowSkipping?: boolean;
         }[];
     }[];
+    /**
+     * The rendered `qti-assessment-item` for an item-ref identifier, or null when it is not on the
+     * page. Looked up when called, so it is never a stale element; ask again after the context
+     * updates (it does when an item is rendered). A function, so `JSON.stringify` leaves it out.
+     * Set by `test-navigation`; for plugins that read an item's content (e.g. text-to-speech).
+     */
+    itemElement?: (identifier: string) => HTMLElement | null;
 };

package/dist/context/types/computed.types.js.map

@@ -1 +1 @@
-{"version":3,"file":"computed.types.js","sourceRoot":"","sources":["../../../src/context/types/computed.types.ts"],"names":[],"mappings":"","sourcesContent":["import type { View } from '../session.context';\nimport type { ComputedItemContext } from './computed-item.types';\n\nexport type ComputedItem = ComputedItemContext & {\n  categories?: string[]; // not necessary for outside world\n  type?: 'info' | 'regular';\n  index?: number;\n  active?: boolean;\n  allowSkipping?: boolean;\n  maxAttempts?: number;\n  showFeedback?: boolean;\n  showSolution?: boolean;\n  numAttempts?: number;\n  valid?: boolean;\n  isDefaultResponse?: boolean;\n  done?: boolean;\n  /** Last *ended attempt* reached the optimal outcome (best achievable score / correct response). */\n  optimal?: boolean;\n};\n\nexport type ComputedContext = {\n  view: View;\n  identifier: string;\n  title: string;\n  testParts: {\n    active?: boolean;\n    identifier: string;\n    navigationMode: 'linear' | 'nonlinear';\n    submissionMode: 'individual' | 'simultaneous';\n    allowSkipping?: boolean;\n    sections: {\n      active?: boolean;\n      identifier: string;\n      title: string;\n      completed?: boolean;\n      items: ComputedItem[];\n      navigationMode: 'linear' | 'nonlinear';\n      submissionMode: 'individual' | 'simultaneous';\n      allowSkipping?: boolean;\n    }[];\n  }[];\n};\n"]}
+{"version":3,"file":"computed.types.js","sourceRoot":"","sources":["../../../src/context/types/computed.types.ts"],"names":[],"mappings":"","sourcesContent":["import type { View } from '../session.context';\nimport type { ComputedItemContext } from './computed-item.types';\n\nexport type ComputedItem = ComputedItemContext & {\n  categories?: string[]; // not necessary for outside world\n  type?: 'info' | 'regular';\n  index?: number;\n  active?: boolean;\n  allowSkipping?: boolean;\n  maxAttempts?: number;\n  showFeedback?: boolean;\n  showSolution?: boolean;\n  numAttempts?: number;\n  valid?: boolean;\n  isDefaultResponse?: boolean;\n  done?: boolean;\n  /** Last *ended attempt* reached the optimal outcome (best achievable score / correct response). */\n  optimal?: boolean;\n};\n\nexport type ComputedContext = {\n  view: View;\n  /** What test plugins keep, by plugin name (`QtiTestState.session.plugins`). Read-only; write with `cito-test-update-plugin-state`. */\n  plugins?: Readonly<Record<string, unknown>>;\n  identifier: string;\n  title: string;\n  testParts: {\n    active?: boolean;\n    identifier: string;\n    navigationMode: 'linear' | 'nonlinear';\n    submissionMode: 'individual' | 'simultaneous';\n    allowSkipping?: boolean;\n    sections: {\n      active?: boolean;\n      identifier: string;\n      title: string;\n      completed?: boolean;\n      items: ComputedItem[];\n      navigationMode: 'linear' | 'nonlinear';\n      submissionMode: 'individual' | 'simultaneous';\n      allowSkipping?: boolean;\n    }[];\n  }[];\n  /**\n   * The rendered `qti-assessment-item` for an item-ref identifier, or null when it is not on the\n   * page. Looked up when called, so it is never a stale element; ask again after the context\n   * updates (it does when an item is rendered). A function, so `JSON.stringify` leaves it out.\n   * Set by `test-navigation`; for plugins that read an item's content (e.g. text-to-speech).\n   */\n  itemElement?: (identifier: string) => HTMLElement | null;\n};\n"]}

package/dist/context/types/item.types.js

@@ -3,7 +3,8 @@ export const itemContextVariables = [
         identifier: 'completionStatus',
         cardinality: 'single',
         baseType: 'string',
-        value: 'unknown',
+        // QTI info model §2.2.2; the item makes it `unknown` once it is presented.
+        value: 'not_attempted',
         type: 'outcome'
     },
     {

package/dist/context/types/item.types.js.map

@@ -1 +1 @@
-{"version":3,"file":"item.types.js","sourceRoot":"","sources":["../../../src/context/types/item.types.ts"],"names":[],"mappings":"AAuBA,MAAM,CAAC,MAAM,oBAAoB,GAAG;IAClC;QACE,UAAU,EAAE,kBAAkB;QAC9B,WAAW,EAAE,QAAQ;QACrB,QAAQ,EAAE,QAAQ;QAClB,KAAK,EAAE,SAAS;QAChB,IAAI,EAAE,SAAS;KAChB;IACD;QACE,UAAU,EAAE,aAAa;QACzB,WAAW,EAAE,QAAQ;QACrB,QAAQ,EAAE,SAAS;QACnB,KAAK,EAAE,GAAG;QACV,IAAI,EAAE,UAAU;KACjB;CAC0C,CAAC","sourcesContent":["import type { VariableDeclaration } from '../../lib/variables';\n\nexport interface ItemContext {\n  identifier?: string;\n  href?: string;\n  variables?: ReadonlyArray<VariableDeclaration<string | string[] | null>>;\n  /**\n   * Optional per-interaction opaque state, keyed by responseIdentifier.\n   * Used for interactions that support state save/restore (e.g. PCI).\n   */\n  state?: Record<string, string | null>;\n  /** The item is shown for reading only. Interactions follow it; see `qti-assessment-item`'s `readonly`. */\n  readonly?: boolean;\n  /** The item is locked, for example after it was submitted. Interactions follow it; see `qti-assessment-item`'s `disabled`. */\n  disabled?: boolean;\n  /**\n   * Whether the interactions in the item are valid right now (a required answer is given, a limit is\n   * respected). Published by the item whenever it checks, so a reader never has to ask the item.\n   * Unset until the item has checked once.\n   */\n  valid?: boolean;\n}\n\nexport const itemContextVariables = [\n  {\n    identifier: 'completionStatus',\n    cardinality: 'single',\n    baseType: 'string',\n    value: 'unknown',\n    type: 'outcome'\n  },\n  {\n    identifier: 'numAttempts',\n    cardinality: 'single',\n    baseType: 'integer',\n    value: '0',\n    type: 'response'\n  }\n] as VariableDeclaration<string | string[]>[];\n"]}
+{"version":3,"file":"item.types.js","sourceRoot":"","sources":["../../../src/context/types/item.types.ts"],"names":[],"mappings":"AAuBA,MAAM,CAAC,MAAM,oBAAoB,GAAG;IAClC;QACE,UAAU,EAAE,kBAAkB;QAC9B,WAAW,EAAE,QAAQ;QACrB,QAAQ,EAAE,QAAQ;QAClB,2EAA2E;QAC3E,KAAK,EAAE,eAAe;QACtB,IAAI,EAAE,SAAS;KAChB;IACD;QACE,UAAU,EAAE,aAAa;QACzB,WAAW,EAAE,QAAQ;QACrB,QAAQ,EAAE,SAAS;QACnB,KAAK,EAAE,GAAG;QACV,IAAI,EAAE,UAAU;KACjB;CAC0C,CAAC","sourcesContent":["import type { VariableDeclaration } from '../../lib/variables';\n\nexport interface ItemContext {\n  identifier?: string;\n  href?: string;\n  variables?: ReadonlyArray<VariableDeclaration<string | string[] | null>>;\n  /**\n   * Optional per-interaction opaque state, keyed by responseIdentifier.\n   * Used for interactions that support state save/restore (e.g. PCI).\n   */\n  state?: Record<string, string | null>;\n  /** The item is shown for reading only. Interactions follow it; see `qti-assessment-item`'s `readonly`. */\n  readonly?: boolean;\n  /** The item is locked, for example after it was submitted. Interactions follow it; see `qti-assessment-item`'s `disabled`. */\n  disabled?: boolean;\n  /**\n   * Whether the interactions in the item are valid right now (a required answer is given, a limit is\n   * respected). Published by the item whenever it checks, so a reader never has to ask the item.\n   * Unset until the item has checked once.\n   */\n  valid?: boolean;\n}\n\nexport const itemContextVariables = [\n  {\n    identifier: 'completionStatus',\n    cardinality: 'single',\n    baseType: 'string',\n    // QTI info model §2.2.2; the item makes it `unknown` once it is presented.\n    value: 'not_attempted',\n    type: 'outcome'\n  },\n  {\n    identifier: 'numAttempts',\n    cardinality: 'single',\n    baseType: 'integer',\n    value: '0',\n    type: 'response'\n  }\n] as VariableDeclaration<string | string[]>[];\n"]}

package/dist/lib/qti-rule-base.d.ts

@@ -20,8 +20,8 @@ export declare abstract class QtiRuleElement extends LitElement implements QtiRu
  * every one of those loops without each of them having to report upwards.
  *
  * `qti-response-processing` catches it at the top of the run. The outcomes set
- * before the exit are kept, because each `qti-set-outcome-value` has already
- * dispatched by the time this is thrown.
+ * before the exit are kept: they are already on the run's working copy, which
+ * the item applies once the run ends.
  */
 export declare class QtiExitResponseSignal extends Error {
     constructor();

package/dist/lib/qti-rule-base.js

@@ -13,8 +13,8 @@ export class QtiRuleElement extends LitElement {
  * every one of those loops without each of them having to report upwards.
  *
  * `qti-response-processing` catches it at the top of the run. The outcomes set
- * before the exit are kept, because each `qti-set-outcome-value` has already
- * dispatched by the time this is thrown.
+ * before the exit are kept: they are already on the run's working copy, which
+ * the item applies once the run ends.
  */
 export class QtiExitResponseSignal extends Error {
     constructor() {

package/dist/lib/qti-rule-base.js.map

@@ -1 +1 @@
-{"version":3,"file":"qti-rule-base.js","sourceRoot":"","sources":["../../src/lib/qti-rule-base.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,UAAU,EAAE,MAAM,KAAK,CAAC;AASjC;;GAEG;AACH,MAAM,OAAgB,cAAe,SAAQ,UAAU;CAEtD;AAED;;;;;;;;;;;GAWG;AACH,MAAM,OAAO,qBAAsB,SAAQ,KAAK;IAC9C;QACE,KAAK,CAAC,mBAAmB,CAAC,CAAC;QAC3B,IAAI,CAAC,IAAI,GAAG,uBAAuB,CAAC;IACtC,CAAC;CACF;AAED;;;;;;GAMG;AACH,MAAM,OAAO,iBAAkB,SAAQ,KAAK;IAC1C;QACE,KAAK,CAAC,eAAe,CAAC,CAAC;QACvB,IAAI,CAAC,IAAI,GAAG,mBAAmB,CAAC;IAClC,CAAC;CACF","sourcesContent":["import { LitElement } from 'lit';\n\n/**\n * Interface for any object that can process QTI rules\n */\nexport interface QtiRuleBase {\n  process(): any;\n}\n\n/**\n * Abstract base class for QTI rule DOM elements\n */\nexport abstract class QtiRuleElement extends LitElement implements QtiRuleBase {\n  abstract process(): any;\n}\n\n/**\n * Thrown by `qti-exit-response` to end the response processing of an attempt.\n *\n * An exit can sit at any depth — inside a `qti-response-condition` branch, or\n * inside a `qti-response-processing-fragment` — and has to stop every rule\n * after it, not just its own siblings. Unwinding the stack is what reaches\n * every one of those loops without each of them having to report upwards.\n *\n * `qti-response-processing` catches it at the top of the run. The outcomes set\n * before the exit are kept, because each `qti-set-outcome-value` has already\n * dispatched by the time this is thrown.\n */\nexport class QtiExitResponseSignal extends Error {\n  constructor() {\n    super('qti-exit-response');\n    this.name = 'QtiExitResponseSignal';\n  }\n}\n\n/**\n * Thrown by `qti-exit-test` to end the outcome processing of a test.\n *\n * The test-level twin of {@link QtiExitResponseSignal}, and unwinds the stack\n * for the same reason: an exit inside a `qti-outcome-condition` branch has to\n * stop the rules after the condition, not just its own siblings.\n */\nexport class QtiExitTestSignal extends Error {\n  constructor() {\n    super('qti-exit-test');\n    this.name = 'QtiExitTestSignal';\n  }\n}\n"]}
+{"version":3,"file":"qti-rule-base.js","sourceRoot":"","sources":["../../src/lib/qti-rule-base.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,UAAU,EAAE,MAAM,KAAK,CAAC;AASjC;;GAEG;AACH,MAAM,OAAgB,cAAe,SAAQ,UAAU;CAEtD;AAED;;;;;;;;;;;GAWG;AACH,MAAM,OAAO,qBAAsB,SAAQ,KAAK;IAC9C;QACE,KAAK,CAAC,mBAAmB,CAAC,CAAC;QAC3B,IAAI,CAAC,IAAI,GAAG,uBAAuB,CAAC;IACtC,CAAC;CACF;AAED;;;;;;GAMG;AACH,MAAM,OAAO,iBAAkB,SAAQ,KAAK;IAC1C;QACE,KAAK,CAAC,eAAe,CAAC,CAAC;QACvB,IAAI,CAAC,IAAI,GAAG,mBAAmB,CAAC;IAClC,CAAC;CACF","sourcesContent":["import { LitElement } from 'lit';\n\n/**\n * Interface for any object that can process QTI rules\n */\nexport interface QtiRuleBase {\n  process(): any;\n}\n\n/**\n * Abstract base class for QTI rule DOM elements\n */\nexport abstract class QtiRuleElement extends LitElement implements QtiRuleBase {\n  abstract process(): any;\n}\n\n/**\n * Thrown by `qti-exit-response` to end the response processing of an attempt.\n *\n * An exit can sit at any depth — inside a `qti-response-condition` branch, or\n * inside a `qti-response-processing-fragment` — and has to stop every rule\n * after it, not just its own siblings. Unwinding the stack is what reaches\n * every one of those loops without each of them having to report upwards.\n *\n * `qti-response-processing` catches it at the top of the run. The outcomes set\n * before the exit are kept: they are already on the run's working copy, which\n * the item applies once the run ends.\n */\nexport class QtiExitResponseSignal extends Error {\n  constructor() {\n    super('qti-exit-response');\n    this.name = 'QtiExitResponseSignal';\n  }\n}\n\n/**\n * Thrown by `qti-exit-test` to end the outcome processing of a test.\n *\n * The test-level twin of {@link QtiExitResponseSignal}, and unwinds the stack\n * for the same reason: an exit inside a `qti-outcome-condition` branch has to\n * stop the rules after the condition, not just its own siblings.\n */\nexport class QtiExitTestSignal extends Error {\n  constructor() {\n    super('qti-exit-test');\n    this.name = 'QtiExitTestSignal';\n  }\n}\n"]}

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@qti-components/base",
   "description": "QTI shared utilities",
-  "version": "2.5.0",
+  "version": "3.0.0-next.4",
   "author": "",
   "dependencies": {
     "@qti-components/utilities": "^1.3.3"