Skip to content

Release v22.125.0

Choose a tag to compare

@github-actions github-actions released this 18 Oct 19:03
82b5d71

Protected read-model key validation no longer depends on trimming- or AOT-unsafe reflection for composite keys.

Added

  • Composite keys of protected read models are validated through accessors the Arc source generator produces, with no reflection. Key types the generator cannot see — partial, external, derived or from experimental assemblies — can be registered with ProtectedReadModelKeyAccessors.Register<T>(...). See Protected key accessors. (#3392)
  • ProtectedReadModelKeyOptions.Strict rejects composite key types that have neither a generated accessor nor a registration, instead of falling back to reflection. Under NativeAOT this is always the behavior. (#3392)
  • Analyzer diagnostic ARC0030 reports a composite key type the generator cannot produce an accessor for. (#3392)

Changed

  • On JIT, a composite key type without a generated accessor or registration is still validated through reflection, and Arc now logs a warning once per such type naming it, so it can be registered before strict validation becomes the default in a future major release. (#3392)