Replies: 1 comment 2 replies
-
Hi @cmenzi, |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello
We are doing some integration testing against Sql Server and EF core, where we also measure index performance of some the columns.
In order to prepare the tests in a generic way for all our LIST endpoints which support filtering and ordering, we like to use the following methods:
IEnumerable<ParsedOrdering> GridifyExtensions::ParseOrderings(this string orderings)
IEnumerable<ISyntaxNode> GridifyExtensions::Descendants(this ISyntaxNode root)
Both, parameters and return values are already public. Would it therefore be issue, to also make this 2 methods public?
Or maybe introduce a
IEnumerable<FieldExpressionSyntax> ParseFilterings(this string filter)
. Also hereFieldExpressionSyntax
is already public.I can call it via reflection, but it does not feel rights ;-)
Beta Was this translation helpful? Give feedback.
All reactions