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

Fix to #20609 - Includes() with string throws not finding navigation path exception when type T is derived #20630

Merged
merged 1 commit into from
Apr 17, 2020

Conversation

maumar
Copy link
Contributor

@maumar maumar commented Apr 14, 2020

Fix is to use logging infrastructure for the "invalid include path" error. Log event is configured to throw by default but can be overriden in the dbcontextoptions. Event id is CoreEventId.InvalidIncludePathError

Resolves #20609

@maumar maumar requested a review from ajcvickers April 14, 2020 20:32
@maumar maumar force-pushed the include_warning branch 2 times, most recently from e275d5c to 92bc7de Compare April 14, 2020 21:46

private BugContext20609 CreateContext20609()
{
var testStore = SqlServerTestStore.CreateInitialized("QueryBugsTest", multipleActiveResultSets: true);
Copy link
Contributor Author

Choose a reason for hiding this comment

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

is this the right way to do custom warnings config in qbt? @AndriySvyryd

Copy link
Member

Choose a reason for hiding this comment

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

No, but it's fine for now. Tracked by #17588

@@ -196,6 +197,20 @@ private enum Id
public static readonly EventId PossibleUnintendedReferenceComparisonWarning
= MakeQueryId(Id.PossibleUnintendedReferenceComparisonWarning);

/// <summary>
/// <para>
/// Invalid include path '{navigationChain}', couldn't find navigation for '{navigationName}'.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

"couldn't" -> "could not"?

…path exception when type T is derived

Fix is to use logging infrastructure for the "invalid include path" error. Log event is configured to throw by default but can be overriden in the dbcontextoptions. Event id is CoreEventId.InvalidIncludePathError
@maumar maumar merged commit c60e710 into master Apr 17, 2020
@maumar maumar deleted the include_warning branch April 17, 2020 03:51
@smitpatel
Copy link
Contributor

Unless I am missing something why the file CoreStrings.Designer.cs has changed but there are no changes in CoreStrings.resx file in this PR?

@ajcvickers
Copy link
Member

@smitpatel I missed that. @maumar You probably made the changes manually, which is fine, but can we get the resx file updated to match?

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.

Includes() with string throws not finding navigation path exception when type T is derived
4 participants