Skip to content

Conversation

gmarz
Copy link
Contributor

@gmarz gmarz commented Mar 21, 2017

…behavioral change in #2367

@gmarz gmarz requested review from russcam and Mpdreamz March 21, 2017 15:12
russcam
russcam approved these changes Mar 22, 2017
Copy link
Contributor

@russcam russcam left a comment

Choose a reason for hiding this comment

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

2 small comments.

Can they both just call base.IsValid?

[Obsolete(@"WARNING: IsValid behavior has changed to align with 1.x and 5.x onwards.
It now returns true for 404 responses (document not found), where previously it returned
false. Please use .Found to check whether the document was actually found.")]
public override bool IsValid => (this.ApiCall?.Success ?? fa[Obsolse) && (this.ServerError == null);
Copy link
Contributor

Choose a reason for hiding this comment

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

Spelling error?

using System.Linq.Expressions;
using Newtonsoft.Json;
using System.Linq;
using System.ServiceModel.ComIntegration;
Copy link
Contributor

Choose a reason for hiding this comment

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

Don't think this directive is needed

@Mpdreamz Mpdreamz removed their request for review March 22, 2017 09:19
@gmarz gmarz force-pushed the fix/isvalid-warnings branch from 7769db1 to 109a5d2 Compare March 22, 2017 13:44
@gmarz
Copy link
Contributor Author

gmarz commented Mar 22, 2017

@forloop good call, fixed.

@gmarz gmarz merged commit 210501a into 2.x Mar 22, 2017
@gmarz gmarz deleted the fix/isvalid-warnings branch March 22, 2017 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants