Blazor allows you to build interactive web UI using C# instead of JavaScript. Blazor apps are composed of reusable web UI components implemented using C#, HTML, and CSS. Both client and server code are written in C#, allowing you to share code and libraries.
Yesterday I accidentally changed the Reset button's type to 'button'. Today I will change it back to 'reset'.
Currently `MyButton` has 3 `[Parameter]`s. If we need to add more, we would have to define new `[Parameter]`s again. To avoid constantly updating this Component, let's use Blazor's `@attribute`.
Now we have an interface to input log entries. But logs are meant to be written every day; how can just one be enough? Let's add a blog.
If we want to add a button to clear the `form` data, the fastest way is to add a `type=”reset”` button. At this point, we use two buttons, which can utilize the core concept of Blazor: component encapsulation.
Now every time you start the project, the default path will be `/`, but we currently don't have a Component using this route. It's a bit troublesome to manually switch to `Post`. Additionally, the Menu icon doesn't match its name. Let's adjust it.
Services you create yourself must be registered in Startup.cs (Blazor Server) or Program.cs (Blazor WebAssemlby), but some basic services don't need to be created by yourself.
Yesterday I saw that the code in `FetchData.razor` was too long. For convenience, we extracted the `@code` section into a separate file.
The C# GitHub page lists a long list of enticing ideas, and some troublesome issues are still under discussion.
The question is, how does Blazor know that WeatherForecastService can be invoked here?