Sieve
QueryR
| Sieve | QueryR | |
|---|---|---|
| 14 | 6 | |
| 1,143 | 32 | |
| - | - | |
| 0.0 | 10.0 | |
| 5 months ago | over 1 year ago | |
| C# | C# | |
| GNU General Public License v3.0 or later | MIT License |
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.
Sieve
-
Junction/association/Link Table VS Join ( Entity Framework Core )
Biarity/Sieve: ⚗️ Clean & extensible Sorting, Filtering, and Pagination for ASP.NET Core (github.com)
-
ASP.NET Core MVC Generic Repository only works with a specific Context. (Need help)
I´m trying out Sieve and the rip my app to pieces and use that instead.
-
Most flexible way to query data from database
Similar to Sieve
- API filtering, pagination and sorting
- How to add non mandatory EF Core Query Filters?
-
Why Microsoft is not pushing hard on OData in rescent .net versions?
https://github.com/Biarity/Sieve Sieve is a simple, clean, and extensible framework for .NET Core that adds sorting, filtering, and pagination functionality out of the box. Most common use case would be for serving ASP.NET Core GET queries.
-
Pagination with dynamic filtering and sorting
If you're looking for a library for a REST API, there really aren't very many good ones. I used Sieve as a starting point to write my own because it didn't support the filtering syntax I was required to use. I would definitely not recommend a new person write their own, however.
-
Clean Ways to Implement Large Filtering on .Net Core API
I also looked at Sieve: https://github.com/Biarity/Sieve but I'm not sure it is 100% hitting what I am wanting. Unless I am just a bork at the end of my day unable to read properly. Any direction in the right area would greatly be appreciated!
-
Extending IQueryable for very long and specific query
For complex queries like this, you don't have a ton of choices. You could use Sieve (https://github.com/Biarity/Sieve) in lieu of your current implementation. I use it specifically in situations to handle filtering/paging/sorting, not as a general way to access data. Most of the time I write an underlying DB view and hook that up to a keyless entity and allow Sieve to do the actual filtering.
-
Dynamically building Linq queries
If you're using EF, you can use https://github.com/Biarity/Sieve
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
What are some alternatives?
CliWrap - Library for running command-line processes
Superpower - A C# parser construction toolkit with high-quality error reporting
api-guidelines - Microsoft REST API Guidelines
dnSpy - Unofficial revival of the well known .NET debugger and assembly editor, dnSpy
Console Framework - Cross-platform toolkit for easy development of TUI applications.
Msharp - M# is a pioneering project that showcases the full range of features and functionalities that a REST web API should possess.
ReadLine - A Pure C# GNU-Readline like library for .NET/.NET Core
Ooze - This package provides simple mechanism for applying filters, sorters, paging to your IQueryable<T> queries.
NFlags - Simple yet powerfull library to made parsing CLI arguments easy. Library also allow to print usage help "out of box".
System.Linq.Dynamic.Core - The .NET Standard / .NET Core version from the System Linq Dynamic functionality.
SharpNetSH - A simple netsh library for C#
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.