mabdullahsari

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';
    }
}

Then I can assume that the column uuid in your table is the PK? $model->getKeyName() should return uuid.

Are you creating a brand new uuid when you create those models? Because Laravel won't do that for you. You should also return false in getIncrementing because you are not using AI PKs. Same thing with getKeyType which should return string.

public function getIncrementing()
{
    return false;
}

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

When you call create on a model, it doesn't return the id, but a brand new model with the id set in that model, so I'm a bit confused about that. Do you expect to receive an integer from create? You should call $model->getKey()

Your 2nd question, you can manually set the relation on the object so you don't have to hit the database. You already have the properties in this case, so inside your if statement:

$model->setRelation('properties', $request->get('properties'));

This question has been asked many times before, as a matter of fact, the most recent one is from a couple of hours ago.

https://laracasts.com/discuss/channels/code-review/hasmanythrough-cant-eager-load-with-a-take-limit-or-first

I'm pretty sure you run into the same issue as I've explained in this topic

https://laracasts.com/discuss/channels/eloquent/select-limit-of-items-in-hasmany

Instead of chaining the orWhere after the where, try putting it inside the closure you pass into the where. Something like:

Auth::user()->orders()->where(function ($query) {
            $query->awaitingPayment()->orWhere->awaitingPaymentPaypal();
        })->get();

You need to look deeper in the stack trace to catch that pesky bug.

I'm afraid noone can help you, since the information you've provided is very little.

You need to tell the database what kind of "weight" your string values have in order to properly order them.

Assuming you are using MySQL, you can use the FIELD function in order to do this easily. Something like this:

$builder->orderByRaw('FIELD(size, "SM", "MD", "LG", "XL", "XXL")');

You can read more about the particular function in this link https://www.w3resource.com/mysql/string-functions/mysql-field-function.php

Do note that if you are using SQLite for testing, this will cause you trouble. In that case, you will have to use CASE ... WHEN ... THEN in your order clause (because in the end, that's what the FIELD function does behind the scenes)

Components were added to Blade with L5.4, but you are using 2 versions prior?

Well, you just call values() on the collection.

Edit: array_values if after the array operation.

There is no API authentication in "the React way". It is the same process for everything, regardless of the used rendering library/framework. You need to deal with the HTTP client.

Most React and Vue apps utilize Axios as the client and Angular comes with its own implementation.

Long story short, any tutorial that is applicable to Vue is also applicable to React and vice versa.

I edited my response above, but chances are you missed it so I'll explain your issue.

When eager loading relations, Eloquent generates a similar query as below:

select * from "product_images" where "product_images"."category_id" in (1, 2, 3, 4) limit 4

So, you are correctly retrieving all relationships, but then limit the whole thing. This is a limitation of eager loading, and the only way (with barebones Laravel) to fix this is by looping over each category and executing a query for each of them which eliminates the purpose of eager loading.

You can use the package (which is a rejected PR actually) above to still leverage true eager loading.

Trying prefixing and suffixing your code with 3 backticks ``` so it is more readable.

This package from staudenmeir (core Laravel contributor) might be of help

https://github.com/staudenmeir/eloquent-eager-limit

It says literally what you have to do if you'd like to customize your query below the first title...

https://docs.laravel-excel.com/3.1/exports/from-query.html#customizing-the-query

You can tidy things up by putting all of that logic in a Form Request and encapsulate your commentable validation in a custom rule. The controller should not worry about validating the data, it should only process it.

https://laravel.com/docs/6.0/validation#using-rule-objects

https://laravel.com/docs/6.0/validation#form-request-validation

Can you show the contents of the updating handler?

Why are you double posting? You have a very similar topic already.

No, you cannot unless you use event projection because the old state is lost at that point.

You could wrap your code in a DB transaction, but what you've described is a valid operation and semantically correct, it's just not what you desired.

https://github.com/spatie/laravel-event-projector

The name change is only to make it clearer for yourself, the relationship is still going to return a collection of users.

You need to loop over the users and put them in a ul or something or you can stitch them together with commas like

$institution->users->map->name->join(', ');

(Assuming the user has a name attribute)

@untymage I answered that in my previous reply as well. He/she cannot

The relationship is a hasMany. Perhaps you should rename it to users instead of its singular form to avoid confusion. xxxMany relationships return a collection of the provided entity. So, in your case you will have a collection/list of users and not one single user.

What are you trying to achieve exactly?

Honestly, this is preference. I always set $guarded to an empty array (ie. disabling mass assignment protection) because I never pass request parameters as is, only after validating the request.

Disabling mass assignment is telling Laravel

"Hey, I know what I'm doing. You need not interfere."

Answering your question: no. Only if you do silly things like

$user->update($request->all())