Thanks for your response. I read about Vuex but I'm not sure if it will be a little too overkill for what I need. Is it very common / a good practise to concatenate two event emits in Vue applications?
Hi I'm building the frontend for my application with Vue and I have the following components:
All the calls to my API are triggered from the dashboard component so, for example, I pass the list of tasks from the dashboard component to the task-list component via props. Both task-list and week components need the list of tasks, that's why I decided to have the dashboard component to wrap both.
The problem is I want to add a delete/edit button in the task-item component but in order to do so, I have to emit an event in task-item, capture it in task-list, emit another event in task-list and finally capture it in the dashboard component and remove/edit the task from the data. It works ok but I'm sure there is a better way to archive this. I've been thinking about saving the list of tasks in the $root.$data but I'm not sure if that's correct.
I had to replace my 2015 macbook a few months ago and after reviewing a lot of models, I went for the Blade Stealth. I was looking for something really portable but and the same time powerfull enough. It has the 8th Gen Intel processor which are quadcores now, 16GB RAM and 512GB SSD. Build quality is awesome, you can say is a Mac running Windows, or Ubuntu in my case. The only complain I have is that the screen is not as bright as I'd like but it's high res (3200x1800). If you are looking for something bigger, they've just anounced the new 15.6" model, which has a 6 core CPU and an nVidia GTX GPU.
Hope that helps. Regards
As bobby said, both do the same although watch keeps an eye on your project and automatically compiles it every time one of the files changes (and is saved). I usually run npm run watch while developing so it automatically compiles it. If you just want to compile it once you can run npm run dev.
dont u have to use the name of the route instead of the path?
<router-link to="subCate">url to example</router-link>