Resource filtering | ASP.NET Core 5 REST API Tutorial 28

preview_player
Показать описание

Hello everybody I'm Nick and in this video I will show you how you can use query string parameters to implement resource filtering in your REST API in ASP.NET Core.

Don't forget to comment, like and subscribe :)

Social Media:

#tutorial #rest #api
Рекомендации по теме
Комментарии
Автор

@Nick, This is a very nice and useful tutorial series. Could you please add another video of the best way to organize this project by splitting the main project to sub projects(As you separated the Contracts to a separate project)

PrabodhaRandima
Автор

Thank you so much, very informative... There's a bug on cached data, when you query data for the first time from database the response is camel-cased and the response from cached data is pascal-cased

murunwascengy
Автор

I am enjoying your content a lot. Thank you. Regarding filtering, and pagination for that matter. Have you ever tried OData? I am using it in my APIs and when used with caution can add great flexibility to an API.

janvandenbaard
Автор

Thanks. Your videos are such a nice tutorial point. I loved it alot. Coule you please also put something for hosting and deploymeny in linux servers and also IIS for versatality? Thanks.

saurabhpaul
Автор

the overall tutorial is great!...but i have one question why aren't you using respository pattern ?

jawadahmed
Автор

Nice! So there is no better way than to have a long method that checks each filter property if it has a value like you mentioned at 7:05 ?

RawnaNOobPro
Автор

Thanks for this great video. I have one question: If paginationFilter == null, you return the posts without filtering by userId. Is that a bug? However, when you demonstrate the functionality in Swagger it all seems to work. Perhaps paginationFilter is never null and therefore the bug isn't showing?

voggorb
Автор

you can use Gridify for that. it's more cleaner and easier way to do Filtering, Ordering, and pagination in your APIs.

alirezanet
Автор

In my case, "GetAllPostsQuery" object is never null. If I don't use any query strings, all its properties will be null / will have default value but not the object. I also found this post on Stack Overflow:

mandealvaleriu