Reached

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, 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 'Usercan only have oneContractwith oneCampaignat a time, but can haveContractwith otherCampaign` at the same 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:

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

My Contract model:

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

My User model:

    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

Front end build issues?

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

@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 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 :)

Hi there,

Why don't you want the routes in the HTML ? That is kinda the whole point with Ziggy :) - if you want to hide some routes you can blacklist them in the config!

Good job, I like the layout and style :)!

Show us more code, the error is not referenced in your posted code :)

Looks like you didn't include your image in the html code, otherwise, it should be very simple:

You have a wrapper container which contains your contact-info content and your image, then you just make the wrapper container a flex container, if you add the rest of your markup (with the image) I can show you how.

Could you show us some code please?

You probably need a symbolic link between your storage folder and your public folder:

https://laravel.com/docs/5.7/structure#the-storage-directory

/home is usually the default that is set for all authentication within Laravel, try to visit e.g. LoginController.php, there you will see that the $redirectTo property is set to "/home", you could try to change it to /nova instead.

Please be aware that this is true for a couple of the other auth controllers that come out of the box with a new Laravel installation

Did you add your javascript also? :)

Yea, definitely use passport for this, it's the easiest i've worked with of the available solutions :)

You can use the package described in this article, we use a similar approach at my job, and it works well!

https://laravel-news.com/laravel-translations-loader

I think it looks alright! You could always refactor some of the parts into further methods if you think they could be reused :)

Are you able to see the comments coming from pusher in the developer console (inside your browser)?

To format your code, use Github-flavored code-blocks: https://help.github.com/articles/creating-and-highlighting-code-blocks/ - its just done with 3 backticks (check the link)

What is this tag you are talking about, is that a custom element you created?

Otherwise, you use the outermost element (in my example the body) to be the container for the rest of your elements (also the dynamic ones), then you attach a click handler to the body, and you then use "#your-slug-selector" as the clicked element. In your AJAX success response you then append/prepend the element to the DOM, if you are still in doubt, please attach some code :)

This is probably mostly a personal preference, but whenever I have logic like this in a controller method, I like to extract it out to a method on my model, so in your case the Attachment model.

You could then give it a nice and readable name that describes what the method does, this way it makes it much easier to scan the controller for future you (or others).

Hope it helps!

Where in the Comments component are you using the Echo.private function? :)

Hi there,

You could extract it to its own class, and then pull in that class whenever you need it.

Then in the constructor of that class, you pull in the API keys. and set it up.

Hope it helps!

@THEWOODCUTTER - You probably have to do this to make it update since the element is dynamically inserted:

$('#parent').on("click", "#child", function() {});

You can ready more about it here: https://stackoverflow.com/questions/8752321/jquery-live-vs-on-method-for-adding-a-click-event-after-loading-dynamic-ht

Let me know if it doesn't make sense to you.

I would use lazy loading of your components, this way Vue will only fetch what is needed, an example:

`const MultiLevelDonutChart = () => import('./Charts/MultiLevelDonutChart.vue' /* webpackChunkName: "js/MultiLevelDonutChart" */);

Then import it in the main component where you want to use it:

export default {
    components: {
        'multi-level-donut-chart': MultiLevelDonutChart
    }
    ...
}

Can't you just pull out the value from the asset_url helper and put it in front of the mix path? :)

Maybe you could look into using this package? https://github.com/spatie/laravel-server-side-rendering

Just Forge :)

Add the withoutExceptionHandling() method :)

public function test_a_workout_can_be_created()
    {
        $this->withoutExceptionHandling();

      ....

@DOUGLASAKULA - Good to hear :)

What's your environment like? Windows? Mac with Valet?

I would write a middleware to handle this on the route level, then if you need to distinguish inside your blade templates it's also really easy to do.

Something like this for your middleware should work:

<?php

namespace App\Http\Middleware;

use Closure;
use Illuminate\Support\Facades\Auth;

class Admin
{
    public function handle($request, Closure $next)
    {
        // "is_admin" should correspond to a column in your user table
        if (Auth::check() && Auth::user()->is_admin) {
            return $next($request);
        }

        return redirect('home'); // Change this to whereever you want to redirect
    }
}

Use sum as you do, and then use the callback to do calculations https://laravel.com/docs/5.7/collections#method-sum

Can you show some more code please?

Store the API key in your .env file, then you can just refer directly to the key where you call the API :)

You could also make a thin wrapper around the API where you include the key in the constructor.

Angular is just ridiculously verbose and overly complicated for the things it does, adapting Vue makes much more sense as it’s pholoaophies are closer aligned to the ones of Laravels.

Saying stuff like “it’s because Laravel sponsored Vue is” is just stupid, and shows a lack of the values that Laravel are built upon.

Valet automatically assigns an SSL.

As to your other issue, the fix for me was to globally update my composer requirements.

There is a Vue-NativeScript implementation now that you could try, I thinks that’s your best bet :)

Bump

Simply: how do you actually customize the template that is being used for the invoices that are sent to the customers email?

I see the receipt.blade.php file, but not all of the information is available from there right away.

Has anyone managed to do this?