-
-
Notifications
You must be signed in to change notification settings - Fork 540
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
XElement .Should().Be() gives false positives. #3
Comments
A proper solution is proposed in http://blogs.msdn.com/b/ericwhite/archive/2009/01/28/equality-semantics-of-linq-to-xml-trees.aspx. I've asked Eric White for permission. |
We got approval from Eric. https://twitter.com/EricWhiteDev/status/449486245236711424 |
Thanks for asking Eric! I wasn't finding an e-mail address and don't use Twitter myself. There is a snag though. The Do you think he might be able to re-license under the |
After discussion with @vossad01, I'm going to implement the normalized comparison through the Should().BeEquivalent() method to prevent confusion with the current behavior. |
Duplicate of #354. |
* Use config.yml FA repo links * Add `repository` config value (required to run locally)
See original CodePlex issue.
The text was updated successfully, but these errors were encountered: