CliWrap VS Sieve

That being said, keep up the good work. I see a lot of potential in combo with libs like https://github.com/Tyrrrz/CliWrap

Check out CliWrap. https://github.com/Tyrrrz/CliWrap

I am using CliWrap to create my own wrapper for the functionality I need from FFmpeg. Works pretty well!

https://github.com/Tyrrrz/CliWrap

Take a look at https://github.com/Tyrrrz/CliWrap for calling another process from one process.

For example, using the great Cli.Wrap library:

We can use Verify to perform snapshot testing and check for the correct output of the program. In order to make things easier and simplify working with process output capturing and invocation, I used CliWrap.

> You can take a look at System.Diagnostics.Process for one of the worst offenders.

Yeah, this is one of my least favourite APIs in all of .NET. My understanding is that the .NET team is planning to redo it in the next few years, but if you want something better right now I highly recommend the excellent CliWrap library: https://github.com/Tyrrrz/CliWrap

I religiously use CliWrap which makes things a bit easier, but still issues on some things like Async Processes and the start thing i spoke about

Biarity/Sieve: ⚗️ Clean & extensible Sorting, Filtering, and Pagination for ASP.NET Core (github.com)

I´m trying out Sieve and the rip my app to pieces and use that instead.

Similar to Sieve

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.

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.

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!

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.

If you're using EF, you can use https://github.com/Biarity/Sieve