Skip to content

Issue with IQueryable Projection in Combination with Sieve/QueryKit #855

Closed Answered by latonz
Seszele asked this question in Q&A
Discussion options

You must be logged in to vote

Nah I think you are good, the problem here is that since these properties are in a nullable disabled context, Mapperly assumes they are nullable and generates the not-null condition. EF core seems to fail to translate non-null conditions on collections (which don‘t make sense from an EF core point of view). As a workaround you can probably enable nullability for the collection properties and set them to non-nullable. I‘ll create an issue that Mapperly should not generate this non-null condition in projection mappings for collections.

Replies: 1 comment 4 replies

Comment options

You must be logged in to vote
4 replies
@Seszele
Comment options

@latonz
Comment options

Answer selected by Seszele
@Seszele
Comment options

@latonz
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants