What is the best way to process data to a view

In my controller i do the following:

creating Eloquent objects And based on the information i get back from the database, i use a function to get extra data. This extra data is want to pass to my view. Currently i create a collection and pass this to the view.

$archiveData = collect();
        
        $archiveData->put('placeId', $activePlace->id);
        $archiveData->put('placeName', $activePlace->place_name);
etc.

This works.

But it causes that i have to deal with an collection array and an object in my view. So i have to work with two methods to get my data. For example.

$objects->first()->geo_type;
$archiveData['placeName']

I know that there are alternative ways to handle the data. But what is the best practice to deal with this kind of things?

Thanks in advance.

LaryAI

2 years ago

Level 58

When passing data to a view in Laravel, it's generally best to keep the data structure consistent to avoid confusion and make the code easier to maintain. Since you're already using Eloquent objects, you might consider using Eloquent's built-in features to attach additional data to these objects. Here's one way to do it:

Use Eloquent Accessors to add custom attributes to your Eloquent model that don't exist in the database but are computed using other attribute values.

For example, if you have a Place model and you want to add a placeName attribute, you could do the following:

class Place extends Model
{
    // ...

    public function getPlaceNameAttribute()
    {
        // Assuming 'place_name' is a column in your 'places' table
        return $this->place_name;
    }
}

Then, in your controller, you can simply pass the Eloquent object to the view:

public function show($id)
{
    $activePlace = Place::find($id);

    // Now you can access the custom attribute like any other attribute
    $placeName = $activePlace->place_name;

    return view('your_view', compact('activePlace'));
}

In your view, you can access the data using object notation:

{{ $activePlace->geo_type }}
{{ $activePlace->placeName }}

If you need to pass additional data that is not directly related to the Eloquent model, you can add it to the view as a separate variable:

public function show($id)
{
    $activePlace = Place::find($id);
    $extraData = $this->getExtraData($activePlace);

    return view('your_view', compact('activePlace', 'extraData'));
}

In your view, you can then access the extraData as needed:

{{ $activePlace->geo_type }}
{{ $extraData['someKey'] }}

Alternatively, you can use the ->with() method to pass additional data to the view:

public function show($id)
{
    $activePlace = Place::find($id);
    $extraData = $this->getExtraData($activePlace);

    return view('your_view')->with('activePlace', $activePlace)->with('extraData', $extraData);
}

This approach keeps your data organized and allows you to access it in a consistent manner within your views. It also leverages the power of Eloquent to keep your controller code clean and focused on business logic rather than data formatting.

mbo

2 years ago

Level 3

@LaryAI the extra data is not in the database. So the example with the model does not work. Or can it be done differently?

The second solution works but gives me what i currently have: {{ $activePlace->geo_type }} {{ $extraData['someKey'] }} two different ways of getting the data. The question is, if there is a way to harmonize that?

Andy-Payne

2 years ago

Level 10

@mbo The class property for a model doesn't have to be a column in the database.

As per the AI response, could you not put the logic within the model and then assign the additional data as class properties so everything is then accessible via the $activePlace object?

class Place extends Model
{
    // ...

    public function getCustomAttribute()
    {
        // Custom logic
        return 'Something';
    }
}

$activePlace = Place::find($id);
dd($activePlace->custom) // 'Something'

Please or to participate in this conversation.