Additional functionality for IsInInput and multi targeting #24
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added IsInInput operator to enable Input.Contains(Property) rules Added additional example usage to cover functionality that exists but was not tested Added EF Core In Memory provider tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added multitargeting from .net framework 4.0 through .net core 3.1
Added IsInInput operator to enable Input.Contains(Property) rules
Added additional example usage to cover functionality that exists but was not tested
Added EF Core In Memory provider tests
I am supporting quite a few legacy projects as well as newer projects using .net framework 4.0, 4.5.2, and 4.6.1, .net standard 2.0, and .net core 2.1 and 3.1 (migration would be better but finding time for regression tests causes issues). To that end the MRE.dll project has Target Frameworks updated to include the various versions and should now support .net framework 4.0 and on
Added the
IsInInputis for rules that testnew []{"option1","option2","option3"}.Contains(obj.prop)Added example usage for
obj.prop1 = obj.prop2(it existed but was hard to find)Added some tests I had written for EF Core using Microsoft.EntityFrameworkCore.InMemory as the provider.