For this release the main focus was on performance optimizations. But unlike previous 0.8.x versions in this release there’s more new features and bug fixes.
Although it wasn’t supposed to be any new preview of Blazor before hitting the final 3.0, we got the new RC1. So before we continue make sure to update your Visual Studio to 16.3 preview 4 and install newest .Net Core SDK before you install the latest Blazorise. Please follow the official guide. If you have followed all the steps you should be safe to get the latest Blazorise 0.8.5.
This is the biggest and the most important change in this release. The main plan for the 0.9 milestone is to refactor and optimize some parts of Blazorise. With this release we’re one step closer to that goal.
For the long time generating CSS class-names was a pretty a big bottleneck. Since class-names had to be regenerated every time a component is initialized the process can noticeably slow down rendering of the page. For regular-sized pages this is not the problem. But if the page contains a large number of components it can become a problem.
After a lot of refactoring the old
ClassMapper is replaced with the
ClassBuilder. Based on my benchmark calculations the new builder is around 40% faster for the worst-case scenarios where a lot of classes need to be randomly generated based on some condition. It could be speed for up to 2-3% more but that would require the change to the builder API and it would be a lot more difficult to use. These optimizations can be safely be said to be final as there is in my opinion no more noticeable room to improve that is worth doing.
The change is visible only in the code-behind so nothing needs to be changed on your side.
When using a submit button inside of
<Form> element the browser will automatically try to post the page. This is the default browser behavior. Because of this a new attribute is introduced to the
<Button> element, called
PreventDefaultOnSubmit. Basically it prevents a default browser behavior when clicking the submit button. So instead of posting the page it will stop it and just call the
Clicked event handler. Pressing the
Enter key will still work just as it’s supposed to do. more
Chart extension now supports
Hovered event callbacks. When clicked on data points in chart, all required details will be returned by the callback that can be used to extract information about the actual data-set. more
<FigureCaption> components that can be used along the existing
<Figure> component. more
- #252 Added
<SelectItem>components to allow definition of default item that can be selected if
SelectedValueis null or empty.
- #226 New
<ValidationNone>component for default message when validation is not yet done.
- #244 Dropdown going out of bounds
- #162 Snackbar not closing (Server-side)
- #222 Validations.ClearAll() Fails to clear validations for second field
- #230 NumericEdit Decimals Property Handling
As always, if you enjoy working with Blazorise please leave a star on GitHub or click on the star-link bellow. Also consider becoming a Patron or donate via Buy me a Coffee or PayPal and help Blazorise developer to work full time on the project!