Is there an efficient way to replace deprecated components?
It seems extremely regressive to have an updated component and manually switch all of the similar ones out and all references to it. I’m also a little confused as well as to what part of the component was updated. It’s happened multiple times, but the one I am referring to right now is the single select drop down.
Totally agree. I have more and more components showing up as Deprecated, it was a ton of work to get them working they way they are now, and it just seems like I have to go back and redo a ton of work. I’m very concerned that something like Datagrid is going to become deprecated, where I have countless hours of work put into, workflows attached to, etc - and then will have to redo everything just go get new features or have my app be compliant.
I’d also be interested in hearing some input on this. As I get further with my builds and closer to releasing, I have an increasing level of nervousness about what I may be signing myself up for in terms of maintaining this UI through weweb’s growth.
Thanks!
Can anyone from @weweb-team weigh in on this? Do I need to worry that deprecated elements will stop working all together or be removed at some point?
Any update on this question @weweb-team ???
Hi @plucky00 
Deprecated elements generally continue to function for a while. However, we do recommend updating your projects to use the latest components when you can.
Like with most web development frameworks and tools, we may eventually remove deprecated components in future updates, especially if they’re blocking progress or causing issues.
That said, we always aim to communicate clearly and give advance notice before any major changes like that. That’s what we did back in September when we had to remove wrappers from some elements to enable better support of standard CSS.
I hope that helps clarify things!