Two levels of composition doesn't work about detached-mapper HOT 10 CLOSED

Your unit test is tracking the entities and that's why it's working.
At line 50 in the unit test please add "db.ChangeTracker.Clear();" (before mapping the 2nd time)
And please add at line 69: await db.SaveChangesAsync(); (you forgot to save the 2nd time)

And then the test will fail with a constraint db error

Now it will work if we eagerly go ahead before await db.MapAsync<>() call and load all the entities from the DB that are in the graph.

If we don't do that than the composition works a single level down.

from detached-mapper.

It works like a charm! Thank you Leonardo, really great job! I love it!

from detached-mapper.

I've also gotten this problem, Although for me it's 3 levels deep. Is there an ETA on this? or general priority.

For now I've just added a simple work around and setting the correct state for these entities myself.

from detached-mapper.

Hey, sorry for the delay...

@tomesendam @traiannemes Could you please help me to reproduce the bug based on this test?
Map Two Levels Integration Test
Please send a pr, or copy/paste or whatever is easier for you...
Thank you!

from detached-mapper.

If I don't forget I'll do it in the afternoon

from detached-mapper.

Thank you @tomesendam!
The one over there is working, if you can please make it fail it would be easier for me to fix.

from detached-mapper.

Hey, were you able to check the test?
Would be possible for you to post an exact copy of the model that is failing?

from detached-mapper.

Hi Leonardo, by any chance any progress on this? I love the work you've done so far. Thanks!

from detached-mapper.

Thank you, and sorry for the loooooooooooong delay (personal issues and don't have any help).
I published 6.0.2 and 5.0.14, would you like to test?

from detached-mapper.

Leonardo, just as a suggestion on tracking delete entities. When a parent-child relation is set to cascade on delete it would be more efficient to just mark the parent with delete status, SQL will take care of the child table. Right now all child entities are marked as deleted and deleted from database before parent table record is, too

from detached-mapper.