Now that a proper OData client is complete, let’s explore what it takes to build out a web client that will run on any modern browser whether it’s on a desktop, laptop, tablet or phone.

Return CreatedAtAction( 'GetTodo', new, todo) įeel free to browse the other controller actions (for example, note how the PATCH endpoint calls the MarkComplete operation when appropriate). Return BadRequest(ModelState) // with an explicit message! NET OData episode that you can watch here if you’re not familiar with OData or need a refresher. Project Astoria was announced to the public in July of 2007. Despite the excitement around GraphQL as a “newer” technology, the capabilities it provides have been available to. It empowers front-end/client-side developers to query data and shape the results, such as only bringing back a subset of available properties and/or navigating complex object graphs. Intrigued? Let’s explore how with a simple “todo” application. It doesn’t matter if your backend is a SQL Server, a NoSQL Cosmos DB instance, or an in-memory cache. I’m talking about out-of-the-box with the power of Blazor and using very stable and mature OData. No, I’m not talking about making the effort to build a glorified GraphQL client and dropping a massive JSON payload to get what you want.

What if you could use the exact same Todo model in your client, with business logic and validations, to provide a form for the user to add and update the list?ĭon’t fret. This would generate the appropriate call to the server to fetch the filtered and ordered list (as opposed to bring the entire list over the network and then filtering it.) “Give me a list of Todo items that are not yet marked complete and order them by the description.”

Online app builder odata feed