🚀 Blazor Blueprint - Version 3 Announcement #137
Replies: 4 comments 7 replies
-
|
So I have been working hard on the new release and I am thinking about prefixing the component names with My reason for this is two fold:
Would love to know what the thought of the community is on this? Note, the next release already contains breaking changes so if I am going to change it, now would be the best time to do it - also while the library adoption is still small (but hopefully growning). Cheers, |
Beta Was this translation helpful? Give feedback.
-
|
Would you be open to having the prefix be simply 'Ui':
It doesn't seem like there are other libraries using such as of the moment |
Beta Was this translation helpful? Give feedback.
-
|
Congrats on the new release, glad to see some of my contributions are included into v3 :) |
Beta Was this translation helpful? Give feedback.
-
|
Blazor Blueprint v3 has been released. There are a lot of changes in this release and as mentioned these are breaking changes. You can see the migration guide here https://github.com/blazorblueprintui/ui/blob/main/V3-MIGRATION-GUIDE.md and the changelog here https://github.com/blazorblueprintui/ui/blob/main/CHANGELOG.md. There are a couple of open PRs on v2, I will see how to bring them into the v3 branch instead. As usual, feedback is always welcome 👍🏻 and I hope you enjoy these updates. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🚀 Blazor Blueprint - Version 3 Announcement
Hi everyone,
I wanted to share a quick update on the direction of Blazor Blueprint.
I’ll be releasing Version 3 soon. This update focuses on refining several APIs based on what I’ve learned since the initial announcement, through community feedback, issue reports, discussions, and seeing how the library is being used in real-world projects.
First, thank you.
The positive feedback, thoughtful issue reports, and help testing fixes have made a real difference. It’s been encouraging to see the project gain traction and to have developers actively engaging with it.
Although I’ve been in software development for over 20 years, this is the first time I’ve released something as open source and watched it grow publicly. It’s been both exciting and educational. I wasn’t expecting to reach Version 3 this quickly.
A bit of context:
This is not intended to be a frequent pattern. I’m still finding the right balance and refining the design philosophy of the library. Going forward, my intention is to maintain backward compatibility wherever possible and reduce the need for major version increments.
What to Expect in v3
I’ll share a detailed change log and migration guidance closer to release.
Until then, thank you again for the support, encouragement, and collaboration. It’s been a great experience so far, and I’m looking forward to continuing to improve Blazor Blueprint UI together.
Mathew
Beta Was this translation helpful? Give feedback.
All reactions