Skip to content
New issue

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

IMaterializationInterceptor.Completion #35386

Open
sjb-sjb opened this issue Dec 26, 2024 · 0 comments
Open

IMaterializationInterceptor.Completion #35386

sjb-sjb opened this issue Dec 26, 2024 · 0 comments

Comments

@sjb-sjb
Copy link

sjb-sjb commented Dec 26, 2024

The callbacks in IMaterializationInterceptor occur on an entity-by-entity basis without any consideration of related entities. For example, on materialization I cannot validate or calculate something that requires a related entity (always included in my queries).

It would be useful to have a materialization interceptor method that is called with an enumerable of the materialized entities after they have been identity-resolved and navigations have been populated. Alternatively, a DbContext event for this.

Commenting that the entities in the enumerable may not be tracked, if tracking was disabled for the query.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant