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.

Sign up for GitHub

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

Jump to bottom

Test: InMemory and Value Comparers #19465

Closed
smitpatel opened this issue Jan 3, 2020 · 1 comment
Closed

Test: InMemory and Value Comparers #19465

smitpatel opened this issue Jan 3, 2020 · 1 comment
Labels
closed-out-of-scope This is not something that will be fixed/implemented and the issue is closed.

Comments

@smitpatel
Copy link
Member

#19406 added support and some logic
Though it had bug for EF.Property so no regression test. Also regression test for indexer property.
@ajcvickers ajcvickers added this to the Backlog milestone Jan 3, 2020
@ajcvickers ajcvickers changed the title Test: InMemory and valueConverters Test: InMemory and Value Comparers Jan 3, 2020
@ajcvickers ajcvickers modified the milestones: Backlog, MQ Sep 11, 2020
@ajcvickers ajcvickers assigned ajcvickers and smitpatel and unassigned ajcvickers Sep 17, 2020
@smitpatel smitpatel removed their assignment Feb 12, 2021
@ajcvickers ajcvickers added propose-close closed-out-of-scope This is not something that will be fixed/implemented and the issue is closed. and removed area-test propose-close area-query area-in-memory labels Oct 20, 2022
@ajcvickers ajcvickers removed this from the MQ milestone Oct 26, 2022
@ajcvickers
Copy link
Member

We recommend against using the in-memory provider for testing--see Testing EF Core Applications. While we have no plans to remove the in-memory provider, we will not be adding any new features to this provider because we believe valuable development time is better spent in other areas. When feasible, we plan to still fix regressions in existing behavior.

@ajcvickers ajcvickers closed this as not planned Won't fix, can't repro, duplicate, stale Oct 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
closed-out-of-scope This is not something that will be fixed/implemented and the issue is closed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ajcvickers @smitpatel