mabdullahsari

This should be what you're looking for:

https://laravel.com/api/6.x/Illuminate/Database/Eloquent/Model.html#method_flushEventListeners

Why don't you simply iterate over the collection and create a Dictionary/Map like structure to group the entities?

The heated discussion above confused me more, so pardon the additional question.

Çalap sabır versin :)

This should be what you're looking for:

https://laravel.com/api/6.x/Illuminate/Database/Eloquent/Model.html#method_flushEventListeners

Can we at least put a little effort to Google the obvious stuff please?

https://stackoverflow.com/questions/23126562/how-to-remove-a-package-from-laravel-using-composer

No, you are updating UserData so you have to add the values to that model in this case.

Well, then it's probably mass assignment. Open up your UsersData model and take a look at fillable, the attribute names must be present in that array (unless you use guarded ofcourse, then the opposite is true).

Within a single test's body, you should generally follow this pattern:

1. Arrange: Prepare everything for step 2, in your case creating a new page
2. Act: Carry out the action, in your case the request for creating a new page
3. Assert: Make sure everything is what you'd expect after step 2.

If there is repetitive set up, you can use setUp to clean up your tests.

Apart from removing withoutExceptionHandling, I don't see any need for improvement. You are clearly implementing the 3 steps I mentioned above!

Could you try

$validated = $this->validate($request, $rules);

I don't think there is a validate method available on Illuminate\Http\Request.

Also, take a look at FormRequests https://laravel.com/docs/6.x/validation#form-request-validation

You need to clarify "does not work". Are you getting an exception (MassAssignmentException)?

Assuming that your request input params have the same name as your user's attributes, you can do the following:

$user->update($request->validated());

I think it's generally accepted that you should never access env variables in app code without the use of the config helper (ie. having a configuration file)

I think it's generally accepted that you should never access env variables in app code without the use of the config helper (ie. having a configuration file)

Gatsby/Gridsome is probably what you're looking for. I'm building my new portfolio site with Gatsby and it offers everything I'd need for such a site. Fully client-side app solution with routing & seamless SSR.

Especially Gatsby's GraphQL API is very powerful, meaning you can also host an entire blog if you'd like in the future without any hassle. (Dan Abramov's overreacted.io is a fine example).

I'm thinking about hosting my site with Netlify's free plan as it's more than enough for what I need and it has some easy to work with form submission solutions which you can also leverage with Gatsby.

But, yeah you need to know a little bit of React/Vue for these solutions :) Laravel seems very "overkill". GL!

PS: Waiting for your findings regarding route param injection in controllers ;)

@jaytee Being able to "ask" the app instance to inject a certain route parameter instead of passing them all one by one would immediately solve my problem, but I haven't had the time yet to delve into the framework code to see whether it is possible or not. Thanks!

@jaytee is adjusting the routes really the only way? Because, the last route parameter will always be the status and the one before that will be the statusable itself. That's why I thought I could dynamically inject the route parameters into the controller by type hinting (regardless of depth of route), but I guess that's not possible as is? A real bummer though if that is the case.

@jaytee I think you've misunderstood. Everything is working, I just have the problem I described in TL;DR.

Not going to undo anything now, it's pretty much done when I find a way to inject route parameters by type hinting...

view accepts an associative array as its second parameter. Simply do:

return view('contemplado.uploads', compact('contrato'));

@jaytee Yeah, and those posts can belong to any model (ie. polymorphism).

@jaytee Yeah I see, my bad.

People can post "status updates" for a given event/project (à la facebook). So it consists of a title, description and optional images. Images have nothing to do with the issue I'm facing.

I have added a TL;DR at the top to summarize what I'd like to achieve.

TL;DR How can I arbitrarily inject any route parameter into a controller via type hinting, ignoring the order of bound route parameters?

Scenario: I have a Status model that can be used with any given model via polymorphism (models Project/Event can have many statuses and Status itself morphs to a statusable).

What I thought that would work:

• Create a Contract called HasStatuses, every model that has statuses must implement it
• Create a Concern for this contract, every model that has statuses must use it
• Via explicit route model binding, resolve the right status when needed
• Inject the Statusable into the controller using the HasStatuses interface so it stays model agnostic
• When a new model needs statuses, just add the CRUD routes with right parameters and controllers => DRYness achieved

Example controller:

    // EditController.php

    public function __invoke(HasStatuses $statusable, Status $status)
    {
        $images = Image::collection($status->getMedia('images'));

        return view('status.edit', compact('images', 'statusable', 'status'));
    }
    

The code above works for the following route: events/{eventId}/statuses/{statusId}, but apparently does not for the following: charities/{charityId}/projects/{projectId}/statuses/{statusId} because the IoC container is injecting the route parameters relative to the order of parameters in the route and completely ignores the type hints? So for projects, this code crashes because the app passes a Charity instance as statusable which is definitely not what I want.

I tried binding the interface in the AppServiceProvider, but still it is injecting all parameters in the "right" order completely ignoring type hints.

    public function __invoke(Request $request)
    {
        $params = $request->route()->parameters();
        $status = array_pop($params);
        $statusable = array_pop($params);

        $images = Image::collection($status->getMedia('images'));

        return view('status.edit', compact('images', 'statusable', 'status'));
    }

I have temporarily settled with the solution above (so it would work), but it is in no way, shape or form the elegance I was striving for. I had to repeat this for all of my CRUD controllers...

How can I solve the injection problem? Any tips would be highly appreciated, because I cannot live with the current piece of code :/

Do not forget to restart php and if you are using a web server such as nginx configuring php.ini might not be enough as the webserver also has a limit in place for POST calls.

https://www.php.net/manual/en/language.oop5.traits.php

Section "conflicts resolution".

OK, my bad I did not read your post thoroughly. I adjusted my first response, that should do the trick.

No in this case (well at least an answer that literally tells you what's wrong), because no exception is being thrown. The code in itself is working, but according to your test it is not. So, by checking your implementation you have to figure out why it is not carrying out the actions you were expecting.

You can make use of the saving event that fires when an Eloquent model is either being created or updated. However, I don't know why you'd want to repeat yourself by assigning it after an update?

Something like this in your model (Edited):

public static function boot()
{
    static::creating(static function ($model) {
        $model->created_by = Auth::id();
    });

    static::updating(static function ($model) {
        $model->updated_by = Auth::id();
    });
}

The unique validator also accepts a third parameter, namely the id of the record to ignore the validation for.

So, if I may assume that you retrieved a vehicle model:

'immatriculation' => 'required|string|max:15|min:6|unique:voitures,immatriculation,' . $voiture->id ,
'num_vehicule' => 'required|string|max:6|min:6|unique:voitures,num_vehicule,' . $voiture->id,

Keep in mind that you should only do this for updates, not for creations.

You are correct with your assumption, that line of code will never trigger the listeners because Eloquent is generating an ad hoc query to permanently delete the user record from the database, ie. there is no user model in the first place to fire the events for.

Change your code to (mind the removal of the parantheses):

$contact->user->forceDelete();

This time, Eloquent does retrieve the user model from the database so the events can fire.

PS: You can listen to the forceDeleting event, so you don't have to do that if-check ;)

routeIs might be what you're looking for:

https://laravel.com/api/6.x/Illuminate/Http/Request.html#method_routeIs

https://usefulangle.com/post/114/webp-image-in-html-with-fallback

I'm not sure if you can access route parameters directly like that.

Try $this->route('toy')->id

Those migrations have already run, so what I'd suggest is that you delete all of the current migrations you have and regenerate migrations for your current database schema using migrations-generator.

https://github.com/Xethron/migrations-generator

You will end up with a "couple" of files which will also speed up testing immensely.

It is not an array, it achieves the same thing as list, namely destructuring;

https://www.php.net/manual/en/function.list.php

Take a look at toSearchableArray

https://laravel.com/docs/6.x/scout#configuring-searchable-data

If I comprehend correctly, you'd like to retrieve all of the users who left a comment, but without "user duplicates" because he/she can obviously leave more than one comment?

Also, distinct should be avoided if possible because it has some performance implications. It won't work in this scenario either because each row from the result set will be different as a whole even if the user data is the same.

You cannot go deeper than one relationship using Laravel's out-of-the-box solutions. Check out this package https://github.com/staudenmeir/eloquent-has-many-deep

Then, you can probably do the following:

public function ratings()
{
    return $this->hasManyDeep(Rating::class, [Product::class, ProductCategory::class]);
}

The Repository pattern is probably what you're looking for. I'd highly recommend this video for an introduction: https://www.youtube.com/watch?v=93ZhGkFIwbA

If later down the road you decide to completely ditch the API and use Eloquent for everything for example, it will be as easy as just swapping the repositories in the IoC container. You won't even have to touch your controllers.

That is still generating an ad hoc query, you are not retrieving the model.

Replace that piece of code with what @jlrdw has suggested and it should work.

$event->information->update($request->all())

Mind the removal of the parantheses!

You are not updating using the model itself... Eloquent is generating an ad hoc query to update the model in the database. You need to retrieve the model first and then update.

@jlrdw Has already suggested it and I'm pretty sure that's the cause.

\Carbon\Carbon::createFromFormat('d/m/Y', $value)->timestamp

You can consult the official docs about Laravel Scout. There is no official driver for ES, but this one is pretty good: https://github.com/babenkoivan/scout-elasticsearch-driver

I'd recommend watching this video, as he clearly explains all of the gotchas

https://youtu.be/UPkqFvjN-yI

TL;DR Databases are not tailored for proper searching, use solutions such as Elastic or Algolia unless the searching is going to stay simple and limited.

https://github.com/beyondcode/laravel-websockets

Well, assuming you have gone with the custom userComments relationship, you can simply add it to the array after an if check.

$withCount = ['comments'];

if (auth()->check()) {
    $withCount[] = 'userComments';
}

Post::withCount($withCount)
...

No need to overthink

2 options:

throw new NotFoundHttpException;

abort(Response::HTTP_NOT_FOUND);

If I understand correctly, you can do something like this:

->withCount(['comments as user_comments_count' => static function ($exists) {
    $exists->where('user_id', auth()->id());
}])

Then in blade you simply check if user_comments_count is greater than 0, in that case the user has commented on that post.

@auth @if($post->user_comments_count > 0)
    You left comments on this post.
@endif @endauth 

Edit: You can also define a dedicated relationship for this case if you think you will re-use the logic, because in the end, what I provided will also achieve the same thing. It depends on you entirely :)

Can you clarify a bit further of what you'd ultimately like to achieve? What do you mean with boolean, is it a column you have in the database, or a computed value?

There are many ways to deal with this problem, but the most common one is to suffix the "duplicate" slugs with an integer value starting from 0.

There is a package published by Spatie called

spatie/laravel-sluggable

which can save you lots of repetitive work. Just use it and you are good to go (unless you really want to use your own implementation).

Take a look at the section Defining Custom Intermediate Table Models

You can always access the pivot model with $model->relationship->pivot

https://laravel.com/docs/6.0/eloquent-relationships#many-to-many

@zyxxyzyxz That's correct.

Okay, you are mistaken with the default value. That is a fixed default value saved in the database. Str::uuid() will only run once when migrating, that's it. New models won't have new UUIDs. You need to set up an Eloquent event handler for the creating event. I'd recommend to put these in a trait so it is only a matter of importing that trait if another model also needs to use UUIDs. Something like below:

use Illuminate\Support\Str;

trait HasUuid
{
    protected static function bootHasUuid()
    {
        static::creating(static function ($model) {
            if ($model->getKey() === null) {
                $model->setAttribute($model->getKeyName(), (string) Str::uuid());
            }
        });
    }

    public function getIncrementing()
    {
        return false;
    }

    public function getKeyType()
    {
        return 'string';
    }
}