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
indexed properties don't "just work" like scalar properties #277
Comments
Marking as P3 and an enhancement (could be a bug, but I don't think we make any promises, so I'm going with "enhancement"). |
I think reasonable default behaviour would be to act like we've got a dictionary back there and return the values that are saved. |
Given the information provided by @flandersen in #293, I updated the title of this issue to include all indexed properties, since I suspect the cause of the two issues is the same. (Of course, indexed non- |
Marking as 2 - Working and P2, since we have a related #293, reported by a user, and assigning to me. |
@afromogli, are you the same AfroMogli that asked the question on StackOverflow? |
Yes, that is correct :) |
Thanks. Just wanted to make sure I was giving proper credit in the 1.21.0 release notes! |
Allright, Thank you!
|
@afromogli, thanks very much for raising this issue. Look for your name in the release notes. 🏆 This issue has been fixed in release 1.21.0. https://www.nuget.org/packages/FakeItEasy/1.21.0 |
Inspired by a StackOverflow question
If a value is set on the "Item property", the next "get" will return the key that was used to set the value, not the value. Check out this setup:
The text was updated successfully, but these errors were encountered: