Identifier of the conflict the mutator was called against.
The conflict's current kind, or 'unknown' if not registered.
The kind the rejected mutator would have moved it to.
OptionalcauseReadonlyfromThe conflict's current kind, or 'unknown' if not registered.
ReadonlyidIdentifier of the conflict the mutator was called against.
ReadonlynameOptionalstackReadonlytoThe kind the rejected mutator would have moved it to.
StaticstackThe Error.stackTraceLimit property specifies the number of stack frames
collected by a stack trace (whether generated by new Error().stack or
Error.captureStackTrace(obj)).
The default value is 10 but may be set to any valid JavaScript number. Changes
will affect any stack trace captured after the value has been changed.
If set to a non-number value, or set to a negative number, stack traces will not capture any frames.
StaticcaptureCreates a .stack property on targetObject, which when accessed returns
a string representing the location in the code at which
Error.captureStackTrace() was called.
const myObject = {};
Error.captureStackTrace(myObject);
myObject.stack; // Similar to `new Error().stack`
The first line of the trace will be prefixed with
${myObject.name}: ${myObject.message}.
The optional constructorOpt argument accepts a function. If given, all frames
above constructorOpt, including constructorOpt, will be omitted from the
generated stack trace.
The constructorOpt argument is useful for hiding implementation
details of error generation from the user. For instance:
function a() {
b();
}
function b() {
c();
}
function c() {
// Create an error without stack trace to avoid calculating the stack trace twice.
const { stackTraceLimit } = Error;
Error.stackTraceLimit = 0;
const error = new Error();
Error.stackTraceLimit = stackTraceLimit;
// Capture the stack trace above function b
Error.captureStackTrace(error, b); // Neither function c, nor b is included in the stack trace
throw error;
}
a();
OptionalconstructorOpt: FunctionStaticprepare
Thrown when a ConflictRegistry mutator targets a conflict that is not in the
openstate, or that the registry has never observed.Remarks
The composite statechart specifies three transitions out of
Open:resolve,ignore,supersede. There are no edges leavingResolved,Ignored, orSuperseded— those are terminal states. Shipping enum tags whose transitions are not specified by the statechart is one of the explicit don'ts of the engine's commitments, so a forbidden transition surfaces as a typed error rather than a silent no-op.The error carries enough metadata for adapter UIs to route the failure to a useful operator-facing message: which conflict id was targeted, what the current kind was, and which transition was attempted.