Ruffles

@carobiscuit just use the Http facade and it will work properly, check the docs for more info.

It's all about the toilet paper!

@kggeorgiev There are 2 things I like about the magic properties:

• Looks cleaner to me
• It handles null values in cases where the attribute could be null, without the need for if checks

@sumonmselim it should be auth()->user()->avatar

I solved it by using the facade as a dependency in the constructor, it's close enough to what I am looking for.

I believe this issue is related to https://github.com/laravel/framework/issues/31565

Ok so I switched my Factory class to use the Http facade instead and it is working as expected.

Is there an alternative way to use dependency injection for the Http client class?

That’s interesting, because for other similar tests, I don’t use the facade (Storage for example) and it works, but it does not work for Http.

Hi,

I am trying to test some external API calls with a fake call using the Http client that Laravel provides out of the box, but for some reason I am not getting the fake version that I have specified, instead it just proceeds to hit the API for some reason.

Here's an example code in my test:

$http = app(Factory::class);
$http->fake(function ($request) use($http) {
    return $http->response(['Status' => 0], Response::HTTP_OK);
});

After this I do something like:

$response = $this->postJson('my-url', $attributes);

and I get the original response from the external API instead of the fake one that i specified in my test.

Anyone have any ideas what am I missing?

That $attributes['body'] part in the controller reminds me of the legacy code base I work on currently.

Sometimes I wish I had $request->body in those projects, what a luxury that is!

I rebuilt my personal website with Laravel, VueJS and TailwindCSS as a single page application for learning purposes.

Check it out and let me know what you think.

Any feedback is appreciated.

https://davorminchorov.com/

Yeah, controllers with __invoke are also known as single action controllers. You can read about that here.

One way would be to disable the timestamps by using protected $timestamps = false; and manually overriding the values in a model event / observer.

More tips like these can be found in his talk from Laracon US.