We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
At the moment if you write explicit code, such as https://jeremydmiller.com/2024/01/31/using-explicit-code-for-marten-projections/?replytocom=48346#respond for an aggregate and you change opts.Projections.LiveStreamAggregation<Gesprek>(); into opts.Projections.Add(new GesprekProjection(), ProjectionLifecycle.Live);
opts.Projections.LiveStreamAggregation<Gesprek>();
opts.Projections.Add(new GesprekProjection(), ProjectionLifecycle.Live);
You get Unhandled exception. System.ArgumentOutOfRangeException: Live cannot be used for IProjection (Parameter 'lifecycle')
Unhandled exception. System.ArgumentOutOfRangeException: Live cannot be used for IProjection (Parameter 'lifecycle')
For the reasons in the article and to prevent code generation bugs, it would be nice to be able to do this
The text was updated successfully, but these errors were encountered:
JasperFx#2941 Tests for: Using Explicit Code for Marten live aggregat…
2786be0
…e projections
efa16f0
ba7b3a2
Ability to use custom aggregations in Live lifecycle, easier recipes …
263a647
…for using explicit code. Closes GH-2941
297170e
Successfully merging a pull request may close this issue.
At the moment if you write explicit code, such as https://jeremydmiller.com/2024/01/31/using-explicit-code-for-marten-projections/?replytocom=48346#respond for an aggregate and you change
opts.Projections.LiveStreamAggregation<Gesprek>();
intoopts.Projections.Add(new GesprekProjection(), ProjectionLifecycle.Live);
You get
Unhandled exception. System.ArgumentOutOfRangeException: Live cannot be used for IProjection (Parameter 'lifecycle')
For the reasons in the article and to prevent code generation bugs, it would be nice to be able to do this
The text was updated successfully, but these errors were encountered: