Release v22.79.0

Added

• Analyzer ARCCHR0020 (warning) reports an EventForEventSourceId whose literal routing names an event source definition together with a stream that definition does not declare, so a typo no longer sends events to a route the command does not describe. Routes that differ from the command's route on purpose stay supported. (part of #2987)
• Analyzer ARCCHR0021 (info) reports legacy string routing on an EventForEventSourceId that spells out a declared definition stream, and offers a code fix that rewrites it to EventSource = typeof(...) and EventStream, so the definition and its concurrency dimensions are kept. (part of #2987)

Changed

• For commands routed through an event source definition, appending a returned EventForEventSourceId whose legacy routing names a registered definition and a stream it does not declare now fails with EventStreamDoesNotBelongToEventSource, as typed routing already did, instead of appending to an undeclared stream. (part of #2987)
• The public constructors of SingleEventForEventSourceIdCommandResponseValueHandler, EventsForEventSourceIdCommandResponseValueHandler and EventsWithConcurrencyScopesCommandResponseValueHandler that do not take IEventSources are obsolete; they skip routing validation. Dependency injection uses the new constructors. (part of #2987)