Replacing deprecated components

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.

1 Like

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.

2 Likes

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!

2 Likes

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?

2 Likes