Reached

@sti3bas wow, amazing! Will look into it!

Great job!

No, make your show endpoint separate from your index for sure.

Something like this: Route::get('/api/members/{member}', '[email protected]');

Yes, works wonderfully.

Seems like your new issue is related to your config, could you post your database config?

I don't think there is any better way if you want to make sure it's persisted across their whole company.

You could create a flag called back_at and make it a timestamp (instead of the boolean), then you can kind of kill two birds with one stone :).

Check for null (which means = false) or if the timestamp is set (which means = true) on that flag.

@audunru thanks for your reply! Using a sandbox is a great idea, although I am not completely sure that Algolia has something like this :/.

Would be great with some kind of API sandbox environment where you could upload a JSON file and mock it this way - perhaps a new side project idea to pursue :)

Did you try what I suggested?

When you create the event just make a loop that runs 5 times, otherwise I am unsure of your question? :)

You could pass the active state in as a prop? :)

Add the values to the $fillable array on the model, or make an empty guarded array (also on the model) :)

protected $fillable = ['category_name', 'category_description', 'category_slug', 'category_image'];

or

protected $guarded = [];

This video series is probably my favorite in a long time, keep up the good work @jeffreyway ! :)

I am writing a bunch of tests to gain more confidence in my codebase. The tests work fine, but as part of the app there is a call that is made with Scout to Algolia and it returns some geobased results. After searching I haven't found a good way to test this behavior, so I was thinking about mocking up the API results from Algolia and then testing against that instead.

My concern is that potentially this will be very brittle, and I am unsure of whether or not it will actually serve my purpose or not.

Does anyone have any experience doing this or something similar? I am not looking for a solution, just some good ideas/advice I guess, my own solution would be to write a class with some different methods depending on what query parameters are sent with the "request".

Thanks in advance!

It actually works with that package, however I had to do some small changes :)

Step one:

I made a new Class called `ContractUser

<?php

namespace App;

use Illuminate\Database\Eloquent\Relations\Pivot;

class ContractUser extends Pivot
{

    public function user()
    {
        return $this->belongsTo(User::class);
    }

    public function contract()
    {
        return $this->belongsTo(Contract::class);
    }
}

I then added a new foreign key inside my intermediate pivot table:

public function up()
    {
        Schema::create('contract_user', function (Blueprint $table) {
            $table->unsignedBigInteger('user_id');
            $table->unsignedBigInteger('contract_id');
            $table->unsignedBigInteger('campaign_id');

            $table->foreign('user_id')->references('id')->on('users');
            $table->foreign('contract_id')->references('id')->on('contracts');
            $table->foreign('campaign_id')->references('id')->on('campaigns');
        });
    }

And last but not least added a new method to the Campaign model:

public function contractUser() {
        return $this->hasOneDeep(Contract::class, [ContractUser::class])->latest();
}

Then when I want to use it:

return Campaign::with('contractUser')->first();

Heavily inspired by this thread on SO:

https://stackoverflow.com/a/56832439

I just found this package, and it has a method called hasOneDeep, that might work, will try it out and report back:

https://github.com/staudenmeir/eloquent-has-many-deep#hasonedeep

@mstrauss thanks for helping out!

hasOneThrough is definitely interesting, and I also looked at it, but I don't think it will work for my setup, it seems to be looking for a campaign_id foreign key on my user model (which it doesn't have), and that is not really an option since I need the user to be able to have contracts with multiple Campaigns at a time (but never more than one with the same Campaign)

The migration for Contracts:

$table->bigIncrements('id');
$table->unsignedBigInteger('campaign_id')->nullable();
$table->foreign('campaign_id')->references('id')->on('campaigns');
$table->timestamps();

Hi guys,

I am building an API where I have 3 different models:

Campaign Contract User

A Campaign can have many different Contract, belonging to many different User. A User can only have one Contract with the same Campaign at a time.

I am using a pivot table as an intermediary between Userand Contract.

I basically want to return a single Campaign with the Contract for the currently logged in user, however I think my relationships are setup wrong for this, because I get a collection of Contract belonging to a Campaign, when all I really want is just one Contract.

My current solution is to loop over all of the Contract and return the one that belongs to the User but that seems really inefficient to me..

My Campaign model:

class Campaign {
    public function contracts()
    {
        return $this->hasMany(Contract::class);
    }
}
    

My Contract model:

class Contract {
    public function campaign()
    {
        return $this->belongsTo(Campaign::class);
    }
}

My User model:

class User {
    public function contracts()
    {
        return $this->belongsToMany(Contract::class);
    }
}

I tried the following, but it returns a collection of contracts as mentioned above, not quite what I want. Any ideas here? :)

auth()->loginUsingId(1);
    return $campaign = \App\Campaign::with(['contracts.user' => function($query) {
        return $query->where('user_id', auth()->id());
    }])->find(2);

Did you completely uninstall the other package? That's probably whats causing issues, if you follow the documentation then it will work (I did it myself a week ago).

Maybe you could try this preset from the creators? :)

https://www.creative-tim.com/product/argon-dashboard-laravel

If you want to get up and running fast (or you don't necessarily want all of the extras that it bring) then use php artisan make:auth otherwise roll your own. :)

When you console.log(response) what is shown to you?

@martinbean awesome and simple solution! I was overcomplicating things with intermediary tables and such, thanks for helping out :)!

@martinbean so the three levels are gold, platinum and diamond, and it’s basically a representation of the customers current status. Certain campaigns will only be shown to customers with a certain level (e.g. Diamond)

@jlrdw thanks for your reply, however my question was not a UI question, but more a database structure question, sorry if that wasn’t clear enough, I will add it to the original question.

Hi guys,

I am about to start a new project where I would like some ideas on the best way to structure things on the database side of things before I start.

Structure:

1. I have Campaigns that are offers which Customers can "accept/choose"
2. I have 3 different Levels which a Customer can "have"
3. Any Campaign can only be accepted/chosen by one Customer

Has anyone got any experience implementing something like this? Any advice would be appreciated!

Best, Casper

I would use an event bus for this (unless you want to pull in something like Vuex): https://alligator.io/vuejs/global-event-bus/

Keyboard shortcuts are handled entirely on the frontend, so there is nothing Laravel specific needed I believe :)