Sieve
CommandDotNet
Our great sponsors
Sieve | CommandDotNet | |
---|---|---|
14 | 3 | |
1,142 | 550 | |
- | - | |
0.0 | 5.9 | |
5 months ago | 3 months 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
CommandDotNet
-
Simple Command line Project Helper (Would love feedback)
Have you seen https://github.com/bilal-fazlani/commanddotnet? Disclaimer: I'm one of the maintainers What you've thrown together does seem similar to CliFx in some respects, as you mentioned in another thread. It looks like a command must be defined as a class. I once created a framework that followed that approach and ultimately found it limiting. I've found it to be more expressive to use methods to define commands, although both are possible with CommandDotNet. For example, we can use the position of parameters in the methods to define the position in the command. Defining operands (positional parameters) via properties, we automatically position them based on position in the file, which was interesting because .net does not guarantee order of properties when reflecting them. We were able to use CallerLineNumber to get this. You might look into that. To answer the question of `Is the use of the project simple and have any benefit over using other parsers?` I'd say that CommandDotNet, CliFx, Spectre and even MS's System.CommandLine have a head start on tackling some of the more complex features and already have some community around them. It think this project has a bit of catchup to do. For example, you can see the CommandDotNet features at https://commanddotnet.bilal-fazlani.com/features/ A lot of the design went into making it a simple as possible to define a command using c# conventions, like parameter positions, NRT, optional parameters, etc. Fore example, we use nullability to determine if an argument is required, although it's also possible to use DataAnnotations or FluentValidations to perform more complex validations. That all takes a bit of time to support. I'd say if you're looking to experiment and play around, keep at it. It's unlikely you're going to get a lot traction in the space though, especially since MS has their own framework. If you want to contribute code that's more likely to be used and seen by others, look at System.CommandLine or one of the other main tools. If you continue with this one, feel free to use CommandDotNet for reference if you'd like hit me up for questions on the discussions, or feel free to bring ideas to CommandDotNet and contribute.
-
How to generate a CLI interface for CRUD operations?
Someone asked a similar question about a https://github.com/bilal-fazlani/commanddotnet/, which is a tool I help maintain.
-
Spectre.Console is a .NET Standard 2.0 library that makes it easier to create beautiful console applications.
Have you seen CommandDotNet by chance? It has an integration with Spectre.Console. It provides some powerful test tools and what I think is a simpler and more flexible way to define commands.You can check out the features page to see what's available.
What are some alternatives?
CliWrap - Library for running command-line processes
Sharprompt - Interactive command-line based application framework for C#
api-guidelines - Microsoft REST API Guidelines
CliFx - Class-first framework for building command-line interfaces
Console Framework - Cross-platform toolkit for easy development of TUI applications.
spectre.console - A .NET library that makes it easier to create beautiful console applications.
ReadLine - A Pure C# GNU-Readline like library for .NET/.NET Core
Fluent Command Line Parser - A simple, strongly typed .NET C# command line parser library using a fluent easy to use interface
NFlags - Simple yet powerfull library to made parsing CLI arguments easy. Library also allow to print usage help "out of box".
SharpNetSH - A simple netsh library for C#
RunInfoBuilder - A unique command line parser for .NET that utilizes object trees for commands.