This is a simple but useful component to display a value along with a label. It contains three elements commonly used together. A div wrapping the whole component, a label, and a paragraph. It also provides a placeholder to display a character or string in case the value to display is null. This feature is fairly important because without it the overall height of the component would be reduced when the value is null, empty, or whitespace potentially producing an …
Author: Michael Bross
In my last post I decided on a few features for a text input component I’ll name InputTextBCA. I plan to append most if not all the components I design with BCA for Blazor Component Authority. I’ve had the experience of trying to use two different libraries of components on the same page and ran into a naming ambiguity error which forced me to use a fully qualified name. I didn’t like doing that. It seemed a bit noisy to …
What features should a component have? Too many and it isn’t as reusable. Too few and it doesn’t provide much benefit. Examining the components that come with Blazor might help to answer this question. Let’s start with the InputText component which can only be used inside the EditForm. This Razor markup provides a green outline after the value is changed. Adding a DataAnnotation like [Required] to the models property and the DataAnnotationsValidator inside the EditForm provides a red outline when …
The effects of Blazor component size on maintenance and reusability When I first started working with Blazor I loved the fact that everything in Blazor was a component and components could be nested in one another. It seemed like a great way to organize a page, keeping the code cleaner and easier to maintain. However I hadn’t developed a strategy for applying it. The team I was working with had a complicated page to build. It seemed like we could …
Starting the journey to become the Blazor Component Authority. …