The current four blogs come from fake data we have written, but normally we won't do this. Instead, there is a button for users to click to increase or decrease the number of blogs.
Blazor allows you to build interactive Web UIs using C#instead of JavaScript. Blazor applications consist 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 type of Reset button to button, and changed it back to reset today.
Currently, MyButton has 3 [Parameters]. If you add them, a new [Parameter] will have to be defined. In order to avoid constantly updating this Component, we use the '@attribute' provided by Blazor.
Now we have an interface where we can enter a log, but a log means writing every day. How can only one article be enough? Let's add a blog.
If we want to add a button to clear the data of the form, the fastest way is to add a button with the name "reset". At this time, two buttons will be used, and we can use Blazor's core concept: component encapsulation.
Now every time you start a project, the default path will be '/', but we currently don't have a Component to apply this route. It's a bit troublesome to switch to 'Post' yourself. In addition, the pattern of the Menu does not match the name. Let's adjust it.
All services you create must be registered with Startup.cs (Blazor Server) or Program.cs (Blazor WebAssemlby), but you don't have to do some basic services yourself.
Yesterday, I saw that the code of `FetchData.razor` was too long. For convenience, we extracted the part of `@code` and made it into another file.
C#'s GitHub page has a long list of tantalizing ideas, some of which are still being discussed.