Annotate JasperFx.Events Projections cluster for AOT (#262, slice 2/4)#265
Merged
Conversation
Second slice in the JasperFx.Events AOT propagation cleanup (#262), following the Aggregation slice (#264). EventProjectionApplication and its supporting types (ProjectionGraph, JasperFxEventProjectionBase, CodeGenerationExtensions, ReflectionExtensions, ScopedAggregationWrapper, ProjectionStage, InvalidEventToStartAggregateException) reflect on projection / event types to build handler delegates via Expression trees + FastExpressionCompiler.CompileFast. The projection and event types are preserved at the registered projection boundary on the caller side. AOT consumers should rely on JasperFx.Events.SourceGenerator-emitted helpers per the AOT publishing guide. Apply class-level [UnconditionalSuppressMessage] with justifications: - Projections/EventProjectionApplication (outer + nested CreatorBuilder<T>): IL2026/IL2062/IL2072/IL2075/IL2087/IL3050 - Projections/ProjectionGraph: IL2072 - Projections/JasperFxEventProjectionBase: IL2075 - Projections/CodeGenerationExtensions: IL2067/IL2072 - Projections/ReflectionExtensions: IL2070 - Projections/ContainerScoped/ScopedAggregationWrapper: IL2087 - Projections/Composite/ProjectionStage: IL2026 (OptionsDescription diagnostic) - Projections/InvalidEventToStartAggregateException: IL3050 (error-message formatter on the exception path) 240 → 176 unique IL warnings (-64) in JasperFx.Events.csproj. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
This was referenced May 13, 2026
This was referenced May 13, 2026
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Second slice in the JasperFx.Events AOT propagation cleanup (#262), following the Aggregation slice (#264).
EventProjectionApplicationand its supporting types reflect on projection / event types to build handler delegates via Expression trees +FastExpressionCompiler.CompileFast. The projection and event types are preserved at the registered projection boundary on the caller side. AOT consumers should rely onJasperFx.Events.SourceGenerator-emitted helpers per the AOT publishing guide.Applied class-level
[UnconditionalSuppressMessage]:Projections/EventProjectionApplication(outer + nestedCreatorBuilder<T>)Projections/ProjectionGraphProjections/JasperFxEventProjectionBaseProjections/CodeGenerationExtensionsProjections/ReflectionExtensionsProjections/ContainerScoped/ScopedAggregationWrapperProjections/Composite/ProjectionStageOptionsDescriptiondiagnostic)Projections/InvalidEventToStartAggregateExceptionWarning delta
JasperFx.Events.csprojIL warnings on this branch: 240 → 176 (-64).Slicing plan (from #262)
Test plan
Refs #262 #213
🤖 Generated with Claude Code