This a such a huge time saver for me, during design phase I usually make the DB desing in YAML first and then add/update according to requirements and once finalised I start making the migration and models manually, now I can generate models, migrations, controllers also 🤯🤯🤯 count me in already
It could be useful for some, but I generally don’t like pulling in a package just to save a few minutes. I like having more control over my migrations/views/factories/tests without having to learn the nuances of a third party package. For this sort of thing, Quick Admin Panel is much more useful imo
sir, how can i return value with multiple pages ? example code return view('user.index', compact('users'); return view('employee', compact('employees);
You can't return multiple pages at once, and I think there is no reason to do so, maybe you talk about returning multiple data in one page? If not then I don't really understand the problem
@@steve-rolandndetsapi5139 Yes sir, I think everyone thinks like that, but the case I got started with how to get the search result data to display in the view and export it to PDF according to the query results.
Thanks for sharing such a useful content, need some hep in another issue SomeModel::with('SomeRelation')->select( 'first_column' , 'second_column')->get(); when i try to run above query, SomeRelation return as null SomeModel::with('SomeRelation')->get(); If i remove select from the query then it works fine, Can you please explain this why?
@@sajidsadeeq4397 you need to add the model's primary key in the select() to make eagerloadings work, and vice versa. Also, you can use the get() to specify columns like you do in select. Ex. ->get(['id','specific_column']);
I actually agree. Code needs to make sense and be readable to "developers" not regular humans. Person with just "internet browsing" experience should not be able to read code fluently. Obviously it is benefit but I am not going to stress over it if 90% devs understand my code perfectly and some very beginner Junior doesnt. its just about experience which comes with time and practice. Again, code needs to be readable and understandable!!!!
what's the deal with YAML? it's a terrible language with tons of caveats and scarily high chance of making mistakes and yet it's the goto choice for CI/CD tools and things like that... just why? and no, it's absolutely not readable, due to lack of braces and proper array syntax it's a complete mess
![BLACK BAG - Official Trailer [HD] - Only in Theaters March 14](http://i.ytimg.com/vi/Du0Xp8WX_7I/mqdefault.jpg)
This a such a huge time saver for me, during design phase I usually make the DB desing in YAML first and then add/update according to requirements and once finalised I start making the migration and models manually, now I can generate models, migrations, controllers also 🤯🤯🤯
count me in already
Sir,
Is it possible to generate services with laravel blueprint ?
It could be useful for some, but I generally don’t like pulling in a package just to save a few minutes. I like having more control over my migrations/views/factories/tests without having to learn the nuances of a third party package. For this sort of thing, Quick Admin Panel is much more useful imo
Does it have option to choose if it's a web or api based creation? Additionally adding it to api routes and creating and returning resources.
Please look into the documentation. But I haven't seen this option specifically.
Is it wrong to do the relationships only on models and eloquent and not in the database with the migrations?
Yes it is wrong, because some database operations may then fail.
Watch my video about it: ruclips.net/video/-77LnBSL2Zk/видео.html
sir, how can i return value with multiple pages ? example code
return view('user.index', compact('users');
return view('employee', compact('employees);
You can't return multiple pages at once, and I think there is no reason to do so, maybe you talk about returning multiple data in one page? If not then I don't really understand the problem
@@steve-rolandndetsapi5139 Yes sir, I think everyone thinks like that, but the case I got started with how to get the search result data to display in the view and export it to PDF according to the query results.
Thanks for sharing such a useful content, need some hep in another issue
SomeModel::with('SomeRelation')->select( 'first_column' , 'second_column')->get();
when i try to run above query, SomeRelation return as null
SomeModel::with('SomeRelation')->get();
If i remove select from the query then it works fine, Can you please explain this why?
In select also pass the foreign key column name.
@@mustafagondalwala5553 thanks, it worked, can you please why we need to do that? i want to understand the picture behind it
@@sajidsadeeq4397 you need to add the model's primary key in the select() to make eagerloadings work, and vice versa.
Also, you can use the get() to specify columns like you do in select. Ex.
->get(['id','specific_column']);
I want to create an e-commerce website with Laravel APIs and a third-party react frontend. Do you think this will work
Yes it will work. Whats problem do you think ?
Thanks for this
Very nice content to me.
Thank you 💞
Thank you!!!!
LIFE_SAVER
Why we need human-readible thing? We are devs, look like humans but are actually not. 🤣 Fun aside, I guess it is useful. Thanks for the video.
I actually agree. Code needs to make sense and be readable to "developers" not regular humans. Person with just "internet browsing" experience should not be able to read code fluently. Obviously it is benefit but I am not going to stress over it if 90% devs understand my code perfectly and some very beginner Junior doesnt. its just about experience which comes with time and practice. Again, code needs to be readable and understandable!!!!
being human is stressful
Update your browser
what's the deal with YAML? it's a terrible language with tons of caveats and scarily high chance of making mistakes and yet it's the goto choice for CI/CD tools and things like that... just why?
and no, it's absolutely not readable, due to lack of braces and proper array syntax it's a complete mess
Use a .yml editor or config your IDE for .yml, if your only reason is non-readability and chance of mistaking
Client conversation -> Dry Wipe Board - > Wireframe -> DB Schema/DDL -> YAML - > Blueprint -> Laravel -> App -> Deploy -> Invoice -> GetPaid .... gets ever nearer? 🧐😂
php artisan blueprint:build clientsApp.yaml -test -deploy -invoice -checkBankAccount 😁
(Only half joking ...)