Laravel Form: From Blade to Vue.js + API 

True, and if you use jquery you can add $.ajaxSetup that will do the same thing.

I do not recommend Livewire. Reason: * Vue has VueX and Vue Router. In addition, super comprehensive. * Vue's community is much bigger so you can find answers to your questions faster and easier. * Vue allows you to create other projects that don't involve PHP. * Using the API, Vue and Laravel are not related so you can work in a more organized way. * When you have mastered Vue you can quickly learn e.g. React. With Livewire you are limited to only Livewire. * Vue's reactivity is easier and SAFER because when Vue renders the DOM, it doesn't use a back-end like Livewire. Plus it's like 2 times faster. * Learning Vue is easy with only limited JS knowledge! In the end, you need to understand logic. Btw, who says we don't love Vue and Laravel? It's a better duo than Laravel + Livewire!

@@legendoffeiyouknow709 You can't come to a hasty conclusion and say that you don't recommend the framework. Have you ever used it and do your own comparison yourself? Personally I use Vuejs and Livewire both technologies are powerful and each to its advantage depends on the type of project we have. I think we should give the developers a chance to use these two technologies and make their own comparisons instead of orienting them with our own choices. Livewire is a very good tool for those who use the PHP language most of the time. Not thought of as a JavaScript developer.

@@Dave-laye Livewire has no advantage over Vue. For example, if I wanted the ability to upload large video files, the best solution is to chunk the file and then upload it. With Vue, it's easy to send each chunk after the previous chunk is uploaded. Livewire can't do this. With relation to,is that when a user uploads a video, for example, Livewire has no client-side preview. So the user is busy waiting for the file to be uploaded. Suppose it's a large 10GB video and the user has slow internet and later finds out it's the wrong file. Oh well, if only a client-side preview could give the user a good insight before clicking the upload button.... but no, it's Livewire, so not optimal in such situations. This is a small example. And yes, Livewire has benefits, but that's only if you combine it with Apline JS, a JavaScript framework. With Vue, you can combine more handily and optimally. Which, meanwhile, is also more convenient if you work a group. In the end, we want to ensure that users can use the website in the most friendly, convenient, clear and smooth way. With Livewire, you are limited for this, and you will always want more.

Yes at the end of the video I mentioned it as a "homework" to build a "loader" spinning while the action is in progress. Maybe will shoot a separate video on that.

Povilas Korop oops must of missed that. But yes a video on that specifically when using Vuex state would be a good watch!

@@tannercampbell maybe a silly question but why Vuex? From my understanding and practice, Vuex is mostly for communication between different components, like a global variable, in this case I think it's enough to have one local variable in this one component, no?

Yes in single component which is fetching data and making any updates that is fine to do that way. I use Vuex as a data store. For example I’ll have a parent vue component which is dynamic table. Inside table I’ll have actions per each row which upon click triggers emitted event to child components that will handle the actions. Where I use Vuex in this example is I’ll dispatch those updates from child component to Vuex that will update the store data. In Vuex store I’ll track the is_loading property so I can know when to re render parent component and show loading animation. In example I’m using Vuex more of way to access and update data in hierarchical level. I hope example helped but I only use Vuex when dealing with components at this level other then that I have them when like you showed in video.

Hi Blair, there are a few ways. One way is to go SPA-way and leave all routing to Vue, with Vue Router, I will talk about it in my next course, coming in a week or two: twitter.com/PovilasKorop/status/1282630612478722048 But if you prefer the Blade-way, then look at component parameters, like with props: vuejs.org/v2/guide/components-props.html

@@PovilasKorop Thanks Povilas, I tested the Blade-way and it works perfect! I look forward to learning more about the SPA method too, this looks very interesting.

It's a separate topic to talk about, not for a short comment. But I would say it's for dynamic elements on the website that you want to make dynamic, like reloading some element on other element change or perform some action like submitting the form, without reloading the whole page. It's mostly for web "applications", not for web "sites".

If I understood your question correctly, yes, you could add the front-end validation and it should happen before hitting the API.

You can't calculate the sum of data from a dataset that doesn't have that data. You need to calculate that sum separately, before pagination, by building a Query Builder: $query = Post::query(); $sum = $query->sum('id'); $posts = $query->paginate(10);

Up

filler?

It's called Form Filler

Povilas Korop link sir

Here it is: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-zinkT7IFoCg.html

Povilas Korop but we need you to do it lively bro

It would be quite a big project, I think, but will add to my long list of ideas, maybe someday.

I don't work with inertia on such a level that I could shoot a video about it. Maybe some time in the future.

@@PovilasKoropcheck inertiajs pingcrm project and see how it works . and thanks for considering it

@@YassineCoding sorry don't have time, for upcoming two weeks all time for content is already scheduled with all topics. Maybe in the future.

I'm preparing a course on Vue + Laravel, so routing will be a part of that. Hope to release in a few weeks.

:u use just one file like welcome.blade.php with a div that has the id that will be used. and then u can use just vue js

I have a full course about graphql, it may help: laraveldaily.com/course/graphql-laravel