api-guidelines
Sieve
Our great sponsors
api-guidelines | Sieve | |
---|---|---|
15 | 14 | |
22,342 | 1,136 | |
0.4% | - | |
9.0 | 0.0 | |
6 days ago | 4 months ago | |
C# | ||
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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.
api-guidelines
-
Mastering API Design: 26 Resources for Software Engineers
📝 "Microsoft REST API Guidelines" [link]
- Ask HN: Any book recommendations for API design?
-
Recommendation reading (books/blogs) for best practices while designing REST APIs
As a companion to this - Microsoft REST API Guidelines on GitHub.
This is a great, thorough and in-depth document from Microsoft: https://github.com/microsoft/api-guidelines/blob/vNext/Guidelines.md
-
Looking for understandable good practices concerning structure of json returned
Thing is, I made some researches this morning, and I found nowhere a "data" wrapper, not in Microsoft API best practices [FR] (client is using Microsoft APIs), not in Microsoft API guidelines, not in OpenAPI offical specifications, nowhere in any blog I found this morning.
-
Everything about APIs
Microsoft REST API guidelines
-
Library for Filtering/Sorting/Pagination Microsoft Style
I'm working on a web API where I'd like to follow the Microsoft API Guidelines. I thought this would be easy, because surely there would be plenty of libraries out there to support their guidelines, maybe Microsoft even has one out there (I thought). I haven't been able to find any.
-
What every ASP.NET Core Web API project needs - Part 2 - API versioning and Swagger
Let's get started. As you might know, there are several ways to versioning API, by URL, HTTP header, etc. We are going to add API versioning by URL.
- Best Practices for REST API Design
Sieve
- API filtering, pagination and sorting
-
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.
short of using graphql, this is as good as you'll get https://github.com/Biarity/Sieve
-
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
-
What patterns, libraries do you use to enable robust search APIs?
My ideal vision is some higher level library that provides the DSL and parsing, and provides a way to either output Expressions for use with IQueryables or some other implementation to inject it into hand-written SQL queries. I have no clue if such a thing is even possible. I've found Sieve and DapperQueryBuilder. It seems like DapperQueryBuilder would support such a use case, using the Fluent API and conditionally adding Selects, Order By, Where, etc. Have you explored something similar? What did you find?
-
Library for Filtering/Sorting/Pagination Microsoft Style
Closest I've found it Sieve, but it requires such heavy modification that I basically have to re-write it.
-
Come discuss your side projects! [January 2021]
I recently released the first non-alpha version of my port of a little known library for sorting, filtering and pagination for .NET Core called "Sieve". My version "Strainer" (how original, I know) adds more functionalities, improves overall adjustability and maintainability. Some highlights:
What are some alternatives?
google.aip.dev - API Improvement Proposals. https://aip.dev/
CliWrap - Library for running command-line processes
Console Framework - Cross-platform toolkit for easy development of TUI applications.
free-for-dev - A list of SaaS, PaaS and IaaS offerings that have free tiers of interest to devops and infradev
ReadLine - A Pure C# GNU-Readline like library for .NET/.NET Core
OpenAPI-Specification - The OpenAPI Specification Repository
NFlags - Simple yet powerfull library to made parsing CLI arguments easy. Library also allow to print usage help "out of box".
CommandDotNet - A modern framework for building modern CLI apps
SharpNetSH - A simple netsh library for C#
spectre.console - A .NET library that makes it easier to create beautiful console applications.
Swashbuckle.AspNetCore - Swagger tools for documenting API's built on ASP.NET Core
awesome-rest - A collaborative list of great resources about RESTful API architecture, development, test, and performance