-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
XML comments for DbContext.Attach unclear #14037
Labels
area-docs
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
customer-reported
good first issue
This issue should be relatively straightforward to fix.
help wanted
This issue involves technologies where we are not experts. Expert help would be appreciated.
type-bug
Milestone
Comments
ajcvickers
added
area-docs
help wanted
This issue involves technologies where we are not experts. Expert help would be appreciated.
customer-reported
labels
Dec 3, 2018
ajcvickers
added
the
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
label
Apr 21, 2019
ajcvickers
added a commit
that referenced
this issue
Apr 21, 2019
* Fixes #15294 - BoolToStringConverter should not check if falseValue or trueValue is empty * Fixes #15266 - Small typo in resource file * Fixes #14037 - XML comments for DbContext.Attach unclear * Fixes #14001 - DbSet.Local does not automatically call DetectChanges * Fixes #13210 - WithExtension suggests that 'this' is updated, as well as returning 'this'
ajcvickers
added a commit
that referenced
this issue
Apr 21, 2019
* Fixes #15294 - BoolToStringConverter should not check if falseValue or trueValue is empty * Fixes #15266 - Small typo in resource file * Fixes #14037 - XML comments for DbContext.Attach unclear * Fixes #14001 - DbSet.Local does not automatically call DetectChanges * Fixes #13210 - WithExtension suggests that 'this' is updated, as well as returning 'this'
ajcvickers
added a commit
that referenced
this issue
Apr 22, 2019
* Fixes #15294 - BoolToStringConverter should not check if falseValue or trueValue is empty * Fixes #15266 - Small typo in resource file * Fixes #14037 - XML comments for DbContext.Attach unclear * Fixes #14001 - DbSet.Local does not automatically call DetectChanges * Fixes #13210 - WithExtension suggests that 'this' is updated, as well as returning 'this'
ajcvickers
added a commit
that referenced
this issue
Apr 22, 2019
* Fixes #15294 - BoolToStringConverter should not check if falseValue or trueValue is empty * Fixes #15266 - Small typo in resource file * Fixes #14037 - XML comments for DbContext.Attach unclear * Fixes #14001 - DbSet.Local does not automatically call DetectChanges * Fixes #13210 - WithExtension suggests that 'this' is updated, as well as returning 'this'
ajcvickers
added a commit
that referenced
this issue
Apr 22, 2019
* Fixes #15294 - BoolToStringConverter should not check if falseValue or trueValue is empty * Fixes #15266 - Small typo in resource file * Fixes #14037 - XML comments for DbContext.Attach unclear * Fixes #14001 - DbSet.Local does not automatically call DetectChanges * Fixes #13210 - WithExtension suggests that 'this' is updated, as well as returning 'this'
bricelam
added
the
good first issue
This issue should be relatively straightforward to fix.
label
May 31, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-docs
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
customer-reported
good first issue
This issue should be relatively straightforward to fix.
help wanted
This issue involves technologies where we are not experts. Expert help would be appreciated.
type-bug
The current XML summary of DbContext.Attach:
The first paragraph describes that the EntityState will always be set to
Unchanged
. But when the key is set it will actually be set toAdded
.This behaviour is described in the second paragraph, but it's described in such a way that that only should be the case on navigation properties of the main entity. Apparently it's also the case for the main entity.
I think this behaviour is great, but the XML summary should specify that it also applies to the main entity.
Example:
Further technical details
EF Core version: 2.1.4
The text was updated successfully, but these errors were encountered: