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

Preserve references bug #1854

Merged
merged 2 commits into from Dec 19, 2016
Merged

Preserve references bug #1854

merged 2 commits into from Dec 19, 2016

Conversation

lbargaoanu
Copy link
Member

I'm not sure about that check, no tests fail :)
Fixes #1794.

@lbargaoanu
Copy link
Member Author

I guess the idea was that when a destination is passed, there's no reason to check the cache, because you have to return the passed destination. I believe now we do exactly that, but through the cache. The fix is simple enough, I'd rather leave it as it is.

Copy link
Member

@jbogard jbogard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is probably just some edge legacy case from weird stuff in the past.

@jbogard jbogard added the Bug label Dec 19, 2016
@jbogard jbogard added this to the vNext milestone Dec 19, 2016
@jbogard jbogard merged commit 59fa254 into AutoMapper:master Dec 19, 2016
@lbargaoanu lbargaoanu deleted the PreserveReferences branch December 19, 2016 15:45
@lock
Copy link

lock bot commented May 6, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators May 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Performance issues and PreserveReferences not working correctly
2 participants