QueryR
Superpower
| QueryR | Superpower | |
|---|---|---|
| 6 | 4 | |
| 32 | 968 | |
| - | 0.0% | |
| 10.0 | 0.0 | |
| over 1 year ago | almost 2 years ago | |
| C# | C# | |
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
QueryR
-
I made a new filtering library for .NET projects
I love it. I did something similar with my QueryR project.
- What C# tools would you like to use that don't exist today?
- Is there an equivalent of Hypothesis (python) for xunit
-
API filtering, pagination and sorting
I of course also take it a step further and feed the parameters to my expression tree generating library QueryR or QueryR.EntityFrameworkCore.
- REST API using dotnet.
-
Introducing QueryR!
QueryR - https://github.com/craigmccauley/QueryR
Superpower
-
I made a new filtering library for .NET projects
Awesome little project you got going on there :) , I've done something similar with Ooze and extracted it to Ooze.Query later. I need to push them to nuget also when I catch some time (I jump back to it from time to time when I have some free space). Cool to see another person using parser construction libs. I see you used Sprache, I went for SuperPower for this situation.
- how would you solve this? Filtering a db model from the api and persisting the filtration rules in a safe and db agnostic way
- GitHub - nreco/nlquery: Parser for end-user search-like queries and rule-based named entity recognition (NER) in context of tabular dataset schema.
-
Would Someone ELI5 Parser Combinators?
Unfortunately I'm struggling. The first problem is choosing which combinator library to go with: Sprache, Superpower, Parlot, Pidgen, Lexepars, etc. etc. Some look simpler to use than others, others more performant, others come with useful parsers built in.
What are some alternatives?
dnSpy - Unofficial revival of the well known .NET debugger and assembly editor, dnSpy
Sprache - A tiny, friendly, C# parser construction library
Msharp - M# is a pioneering project that showcases the full range of features and functionalities that a REST web API should possess.
Pidgin - A lightweight and fast parsing library for C#.
Ooze - This package provides simple mechanism for applying filters, sorters, paging to your IQueryable<T> queries.
CSLY - a C# embeddable lexer and parser generator (.Net core)
System.Linq.Dynamic.Core - The .NET Standard / .NET Core version from the System Linq Dynamic functionality.
FParsec - A parser combinator library for F#
Ooze.Query - This package enables usage of Readable Queries on IQueryable<T> instances. This is a concept where you can write actual expression as a string representation for filtering.
Recognizers-Text - Microsoft.Recognizers.Text provides recognition and resolution of numbers, units, date/time, etc. in multiple languages (ZH, EN, FR, ES, PT, DE, IT, TR, HI, NL. Partial support for JA, KO, AR, SV). Packages available at: https://www.nuget.org/profiles/Recognizers.Text, https://www.npmjs.com/~recognizers.text
FastExpressionCompiler - Fast Compiler for C# Expression Trees and the lightweight LightExpression alternative. Diagnostic and code generation tools for the expressions.
nlquery - Parser for end-user search-like queries and rule-based named entity recognition (NER) in context of tabular dataset schema.