< Summary

Information

Class:	Elsa.Bpmn.Signals.BpmnScopeSignal
Assembly:	Elsa.Bpmn
File(s):	/home/runner/work/elsa-core/elsa-core/src/modules/Elsa.Bpmn/Signals/BpmnScopeSignal.cs

Line coverage

100%

Covered lines:	1
Uncovered lines:	0
Coverable lines:	1
Total lines:	17
Line coverage:	100%

Branch coverage

N/A

Covered branches:	0
Total branches:	0
Branch coverage:	N/A

Method coverage

Feature is only available for sponsors

Upgrade to PRO version

Metrics

Method	Branch coverage	Crap Score	Cyclomatic complexity	Line coverage
get_Code()	100%	1	1	100%

File(s)

/home/runner/work/elsa-core/elsa-core/src/modules/Elsa.Bpmn/Signals/BpmnScopeSignal.cs

	#	Line		Line coverage
		`1`		`using System.Text.Json;`
		`2`
		`3`		`namespace Elsa.Bpmn.Signals;`
		`4`
		`5`		`/// <summary>`
		`6`		`/// Carries the interpreter's <c>SignalEnclosingScope</c> command from a nested BPMN scope to the scope that started it.`
		`7`		`/// </summary>`
		`8`		`/// <remarks>`
		`9`		`/// The signal travels the ordinary Elsa channel, so it is delivered to the sending scope first and then to each`
		`10`		`/// ancestor in turn. Only the scope that started the sending scope's unit of work claims it; every other receiver`
		`11`		`/// lets it keep bubbling, which is also how a scope that cannot match an escalation re-signals it one hop further`
		`12`		`/// out. There is deliberately one code per kind of scope signal rather than a growing namespace: BPMN escalation`
		`13`		`/// travels under <c>BpmnInterpreter.EscalationSignalCode</c> with its identity in the payload.`
		`14`		`/// </remarks>`
		`15`		`/// <param name="Code">The signal code.</param>`
		`16`		`/// <param name="Payload">The signal payload.</param>`
	9	`17`		`public record BpmnScopeSignal(string Code, JsonElement? Payload);`

Methods/Properties