-
-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
π€Ήπ»ββοΈ Framework stability in Vue Ecosystem & my vision #222
Comments
This is a good proposal @jd-solanki ! π Although I had a similar idea in mind to create a UI library that handle this exact problem, which is to provide high level components, and at the same time low level (Radix Vue) component with a consistent theming capabilities. And with your suggestion of framework guidelines with consistent naming convention, I believe that would reduce the fear of updating major version. π I do however foresee some challenges regarding implementing a framework guidelines that would be adopt by every framework, but we can definitely start somewhere! |
Hi, Thanks for the write, I agree with most of the things you mentioned here but one "Mix low-level and high-level API/props" https://mui.com/material-ui/react-alert/
|
Today, I had another thought π I'll address these issues in framework guidelines/solutions
|
Readers of this issue might be interested in this new repo, Check README. |
@jd-solanki I'd recommend putting a node at the top of the official docs and GitHub repo to tell people about the state of the ui framework, so they don't start a brand new project with it. |
Every upgrade to the current front-end project, be it a UI library or tool chain, is a disaster |
Hi ππ»
I have something to share and I guess you are related to this thing as well.
I'm JD, Author of Vue UI framework Anu. You can read why I created Anu here. After Nuxt UI get released (it was nice lib and can fulfill what I was trying to do with Anu) and due to full time job burden I wasn't able to work on Anu as expected at the start.
I'm writing this because I recently realized few stuff I written below and anu reached the 970+ stars which I thought it won't after taking a break from it.
The Problems
After doing some wild work I found still Vue UI frameworks are not satisfying to me. Every UI framework has its pros and cons. For example,
UI frameworks are not stable with their API because we don't have any guidelines on how we should name our props and what slots we should provide as a framework. This makes framework to introduce new API changes as they evolve and author's mind/vision changes. E.g. Vuetify calls alert detail prop "text" where nuxt UI call it "description" etc. Vuetify made data-table slot name changes recently that broke our existing app and had to rename slots everywhere.
(it might look similar to 2nd point) Years passes and framework changes but project stays the same. After project get finished and you wish to upgrade deps to latest after a year or two, framework that project relies on changes few stuff making framework not future proof and we have to carefully upgrade to latest version using release notes.
The Solutions
AlertTitle
&AlertDescription
. This way, user will have full flexibility with style & structure.is
,should
, etc.The Conclusion
Edit:
The text was updated successfully, but these errors were encountered: