In part 3 of the Keyhole Blazor Server in .NET 6 series, we installed a free component library called Radzen.Blazer, updated the CharacterInfo component to easily display a Create Character modal, and added the RadzenDialog as a way to standardize our dialog with an easy-to-use component. In the next blog, we will be adding events in our blazor components. See you in part 4!
In Part 2 of the Keyhole Blazor Server in .NET 6 series, we learned how to utilize Blazor Protected Browser Storage. We also covered how to build a base component and implement ProtectedStorage on the Characters Page.
Hopefully, you also found that using ProtectedSessionStorage to scope to the current tab allows you to avoid bugs and confusing behavior across multiple tabs. In the next blog, we will cover the installation of Radzen Blazor – a free component library for Blazor. See you in part 3!
Recently on a client project, I was tasked with creating an Angular application that contained a form that displayed conditional inputs. In this article, I will walk through the strategy I implemented to accomplish this goal.
My hope is that this blog will give you a starting point for creating your own complex Angular Reactive forms. Let’s get started!
In Part 1 of the Keyhole Blazor Server in .NET 6 series, we learned how to create a new Blazor server application with both the CLI and Visual Studio methods. We covered the default template files that are provided when creating a new application and talked through some of the functionality and syntax inside the default components.
This gave us a brief primer for creating our own Character Builder application, so we created a Blazor page, navigated to our new page, and created a component to display data on a Character Page. We were able to see how component lifestyles function when attempting to display our characters as well.
Hopefully, Part 1 provided a helpful outline for navigating the CharactersPage component in further installments of the .NET 6 series. See you in Part 2, where we build on this application to utilize Blazor Protected Browser Storage.
Web application users are accustomed to canceling a popup (aka dialog or modal) by pressing the escape key, and many modals can even cancel if the user clicks outside it. How does a React developer code that without a plumbing mess between the modal and every visible component beneath it? How do you cancel a React modal with an escape key or external click?
I’m glad you asked because I have an answer. In this blog, I’ll show a pair of easy-to-use custom React hooks that simplify the task.