6 ms·
We use Vue at GitLab. You can see why we chose Vue as written by our front-end lead. https://about.gitlab.com/2016/10/20/why-we-chose-vue/ https://about.gitlab
by CapnCrunchie 9y ago
We use Vue at GitLab. You can see why we chose Vue as written by our front-end lead.
https://about.gitlab.com/2016/10/20/why-we-chose-vue/ https://about.gitlab.com/2016/10/20/why-we-chose-vue/
- ElatedOwl 9y ago>A simple, but practical example we're using in production: on a GitLab Issue, the issue's state is displayed as either closed or open. That simple value can change often and needs to be represented in several views. With JQuery, we had about 30 or so lines of code to propagate those changes, and those lines involved multiple classes and querying the DOM by hand. Yep, been there. That type of jQuery gobbledygook has resulted in more bugs than I'd like to admit slipping past my team. Vue has been an absolute life saver.
- pythonaut_16 9y agoIs there any plan to do a follow up post to this? I'd love to see what work flows or examples you guys are using to progressively upgrade pieces of the application to use Vue. For example, it would be really great to see a blog post with a before and after for a feature that you've converted from jQuery to Vue.
- CapnCrunchie 9y agoThis was the followup post our front-end lead wrote: https://about.gitlab.com/2017/02/06/vue-big-plan/ https://about.gitlab.com/2017/02/06/vue-big-plan/ I don't think it's exactly what you were asking for, but I'll pass this suggestion along to our front-end lead that wrote these two posts.