bobbybouwmann

@bikashkatwal Awesome!

You can customize the messages in the resources/lang/en/validation.php file.

'custom' => [
    'appointedd_appid' => [
        'required_if' => 'You custom message here',
    ],
],

Documentation: https://laravel.com/docs/5.8/validation#custom-error-messages

@punksolid is correct, middleware is the best place to do this!

You can probably just do this

->when($request->has('search'), function (Builder $query) use ($request) {
    $query->join('eleves', 'retours.fk_eleve', '=', 'eleves.id')->orderBy('eleves.nom', 'asc')->select('retours.*');
})
->paginate(5);

If you want to see the actual query, you can replace paginate(5) by toSql(). It will then output the sql query, so that might be useful for debugging purposes ;)

I would probably create a directory called Services in my app directory and then add the classes for that kind of communication in there. This way it's isolated from the rest, but also reusable on different places.

It seems that the error comes from the mlanin/laravel-api-debugger package. Have you tried removing or disabling it to check if your controller works correctly?

Also your response in your ajax call should be key value based. So someting like this

return response()->json([
    'domains' => $client->domains,
    'projects' => $client->projects,
], 200);

It could be that this already throws an error and that the laravel-api-debugger can't handle that error and throws an error as well :P

You're probably running an old PHP version. If you run php -v on the command line you get the current installed PHP version. I expect you're running something like PHP 5.5.

If you upgrade to at least PHP 7.2 and you run composer create-project again it should install Laravel 5.8.x

Let me know if that works for you!

I think the issue here is that you call make on the factory and not create. When you do make you get a Cat model, but without an ID. It won't be saved in the database. So updating it to this should put you in the right direction

$cat = factory(Cat::class)->create();

The or helper method has been removed since Laravel 5.7 as you can read here in the upgrade guide: https://laravel.com/docs/5.7/upgrade

Instead you can use the native php function for that

{{ $status ?? 'Unknown' }}

This is called the "null coalesce" operator. Let me know if that works for you!

Assuming again that you've setup your relations correctly you can do something like this

$cat = Cat::withCount(['shows', 'attributes'])->first();

$cat->shows_count;
$cat->attributes_count;

Your code looks correct to me. Are you sure the javascript is compiled?

Also I would change the v-for to something like this instead

<li v-for="category in categories" v-bind:key="category.id">
    {{ category.title }}
</li>

Assuming that you've setup the correct relationships between user and category, basically user_id column in the categories table, you can do something like this

$categories = Auth::user()->categories()->orderBy('updated_at', 'desc')->paginate(30);

Let me know if that works for you!

You need to use required_with when using checkboxes

return [
    'isbooking_enabled' => 'sometimes',
    'appointedd_appid' => 'required_with:isbooking_enabled,on',
];

You can probably split the incoming string by each space and validate each parts separately using Carbon. It's not ideal, but it's something!

Awesome! Let me know if you have more questions, I might be able to help ;)

Basically you only need to start horizon. Horizon will make sure that Redis will be connected in Forge.

Check this video: https://laracasts.com/series/learn-laravel-forge/episodes/5

Laravel Passport is build on the thephpleague/oauth2-server package. They have pretty good documentation on oauth and what kind of grant you should pick

Documentation: https://oauth2.thephpleague.com/authorization-server/which-grant/

Going through that complete documentation is definitely worth it!

You need javascript to make this work. Even if you put all the possible options in the HTML you still need a way to display them!

Also doing an ajax call is a good practise for this use case!

It seems that this was added in 5.5: https://github.com/laravel/framework/pull/22119

Anyway, instead of returning early in your job you can check if the model has been soft deleted or not and than return early! Checking on the deleted_at column is perfectly fine ;)

if ($model->trashed()) {
    return;
}

It probably doesn't work in create because it's empty!

Also looking at the form, first you pass in $data which is probably an array, but in the other example you pass in a boolean. So it seems that you're using two types of data here. You need to make sure that the types are the same.

For example for create view you could just pass in false.

Well in this case your TimesheetsController should only have index method which displays a list of the given resource. So for example a list of posts or in your case a list of different kind of timesheets.

Then for each timesheet you can create a specific controller. For example CurrentMonthTimesheetController which only has a show method.

Another solution is using the __invoke method for each controller that you have. This way you don't have to specify a index or show method. You will only have the __invoke method that will return the correct result in each controller.

Documentation: https://laravel.com/docs/5.8/controllers#single-action-controllers

So in your example you would have something like this

Route::get('timesheets', TimesheetsController::class)->name('timesheets.overview');
Route::get('timesheets/current-month', CurrentMonthTimesheetController::class)->name('timesheets.current-month');
Route::get('timesheets/last-month', LastMonthTimesheetController::class)->name('timesheets.last-month');

Let me know if that is a valid solution for you!

@bugsysha I do this daily ;) Fast fingers!

Object itself is not a valid keyword in PHP. You do have the lower key version for that though: object. Anyway, with PHP the return type should match the actual class, otherwise strict typing wouldn't make sense!

So you should update it to this

use Illuminate\View\View;

class ComputersController extends Controller
{
    public function index(): View
    {
        $computers = Computer::all();

        return view('computers.index', compact('computers'));
    }
}

Let me know if that makes sense to you ;)

A non PHP alternative might be cypress! It's written in JavaScript and you write your tests in JS, but you will get video recording support and it's a lot faster than Laravel Dusk as well!

https://www.cypress.io/

You can calculate the date by doing a diff between two dates.

$age = Carbon::parse($patient->dateOfBirth)
    ->diff(Carbon::now())
    ->format('%y years %m months  %d days');

Do you get any errors? Does your database return results?

Also you're using mysqli in your view, this is a really bad solution in PHP. mysqli is not supported anymore, Laravels internal database query class can help you with this!

The internals of Laravel is doing the exact same thing for policies and using the Gate facade as well. This is perfectly fine ;)

You can do one more improvement and that is adding caching for the permission queries. If you get a lot of permissions the pages might load a bit slower ;)

Have you looked into the the groupBy or mapToGroups method of the collection class?

Documentation: https://laravel.com/docs/5.8/collections#method-groupby

Check this part of Laravel: https://github.com/laravel/framework/blob/5.8/src/Illuminate/Foundation/Exceptions/Handler.php#L190

As you can see here Laravel checks if it should give back a normal or json response. So if your request has the correct headers, it will respond with json.

You can then throw any exception or use abort for example to deny access.

I don't see any xml...

Laravel and Vue indeed ;)

Jeffrey also uses algolia for the search functionality, I'm not sure if that is in combination with Laravel Scout.

Another solution is grouping the results by the user using the collection methods, but that is all up to you ;)

Documentation: https://laravel.com/docs/5.8/collections#method-groupby

Perfect!

@click Some people update the initial migrations and therefore they lose all there data because they need to remigrate the whole database. Not everyone is known with this approach ;)

If you have a migration that adds one column with a default value, it won't delete the other entries in the database. One important thing is that you set a default value for that column or make it nullable! So your migration will look like this:

public function up()
{
    Schema::table('cars', function (Blueprint $table) {
        $table->integer('seats')->default(5);
    });
}

So you need to create a new migration using php artisan make:migration add_seats_cars_table to be clear! If you run php artisan migrate the column will be added without losing any data ;)

It seems that you need to pass the slot="activator" parameter to the badge component

Source: https://github.com/vuetifyjs/vuetify/issues/3178

In the bug report you can also find some links to code examples on codepen

You can do something like this in your view

@foreach ($job->sub_jobs as $sub_job)

    @if($loop->first)
        {{ $sub_job->user->name }} <br>
    @endif

    // Display the sub_job content here

@endforeach

Documentation: https://laravel.com/docs/5.8/blade#the-loop-variable

../ indicates that the file is in the parent directory. So if it's placed in the same file as the .env this shouldn't match right?

Another option is being really specific about the location of the file

putenv('GOOGLE_APPLICATION_CREDENTIALS=/home/user/www/XXXXXXXXa8006b.json');

Wouldn't it better if you just did this

 <li class="{{ $serv->id == 1 ? 'active' : ''}}">
    <a data-toggle="tab" href="#{{ $serv->id }}">
        {{ $serv->type }}
    </a>
</li>

At this point if you have two services with the same type you get a duplicate tab, like you have right now. To fix this you should already do that in the query process, you don't want all this logic in your view! You should grab all the results you need in the controller and then pass it to the view ;)

So what it does is look for any children using children() call on the current query. Then it uses with to get call it's own method called childrenRecursive. Basically you're also loading those relationships on the current object. Now whenever this childrenRecursive is called it will again look for any children and then the childrenRecursive will be loaded again on the query.

It will keep doing this until the children() returns an empty result. After that the childrenRecursive isn't loaded anymore and it will return the final result.

You're not using the default primary key, but Laravel doesn't know that! So you need to tell your Invite model that:

class  Invite extends Model
{
    public $incrementing = false;

    protected $keyType = 'string';
}

Let me know if that works for you!

If you use the request() helper or Request:: facade you should be good to go ;) You can't inject a class in the model observer for that.

Shortcodes have to be parsed in a later state, after the content has been generated. You can probably build this with a middleware.

However there is very nice package for this! You only need to write the classes that handles the conversion: https://github.com/webwizo/laravel-shortcodes

Let me know if this is what you're looking for!

Well you need to do the calculation somewhere right? So you either get the numbers from the request or your have to combine the two in the frontend already. You can for example use momentjs for that.

I'm not sure if I understand your question 100%, can you maybe explain a little bit more about it?

It seems that you're using the Laravel Collective HTML /Form package. Did you install this package?

Documentation: https://github.com/LaravelCollective/docs/blob/5.6/html.md

It shows how to set it up and how to use it ;)

@snapey Jep! It's a mess..

Yeah you can! You look into mapToGroups ;)

Documentation: https://laravel.com/docs/5.8/collections#method-maptogroups

The fact that it returns file.png is already odd! Have you tried not passing a name for instance? Does it still return the same thing?

Yeah the Maps Javascript API is what you need!

I guess it depends on what your definition of a "view" is. Is a view any page reload than the current implementation is correct. If your definition of a view that each view is connected to a unique user than this is not the correct implementation.

Maybe Jeffrey can share his view on this?