How does this Facade works

 Question : 

The bounty expires in 6 hours. Answers to this question are eligible for a +50 reputation bounty. nagidi wants to draw more attention to this question.

I'm working with Laravel 5.8 and it's an Online Store project written by other programmers.

Basically I have faced something weird that never seen before.

Let's say we have this at a Controller method:

$payment = CourseRegistrationFacade::insertCourseRegisterInformation($courseId,$date,$memberId,$userId);

And then we goto the CourseRegistrationFacade and it goes like this:

class CourseRegistrationFacade extends BaseFacade
{
    
}

So the whole class is empty but it extends another Facade which is BaseFacade and it goes like this:

class BaseFacade extends Facade
{
    protected static function getFacadeAccessor()
    {
        return static::class;
    }

    protected static function shouldProxyTo($class)
    {
        app()->bind(self::getFacadeAccessor(), $class)
    }
}

And that's it !

I don't really know where the heal is insertCourseRegisterInformation !!

So if you know how this Facade works, please let me know...

---

Here is the full code of BaseFacade.php:

namespace App\Facades;

use Illuminate\Support\Facades\Facade;

class BaseFacade extends Facade
{
    protected static function getFacadeAccessor()
    {
        return static::class;
    }

    public static function shouldProxyTo($class)
    {
        app()->bind(self::getFacadeAccessor(), $class);
    }
}

Answers

Search in the code for:

CourseRegistrationFacade::shouldProxyTo(

Most likely in the service provider that line is somewhere registering that facade to some concrete implementation of a class. Then check the contents of the class (the argument passed to shouldProxyTo).

Inside that class there should be a method called insertCourseRegisterInformation.

The way facades work is they resolve the class out of the container and then call the method you call statically.

So for example, let's say you have a UserService.php with a method register() and that class is mapped to a UserServiceFacade.php. When you do UserServiceFacade::register(), __callStatic will get the facade accessor (actual class) from the container, then call the register() method of that class.

You can understand better by inspecting __callStatic inside Facade.php.

Essentially UserServiceFacade::register() is the same as doing:

$userService = app()->make(UserService::class);

$userService->register()

By using the facade you can hide the concrete implementation and could possibly switch it to something else in the future by just changing it in a single place.

Read More

Socialite Implementation for Laravel Jetstream

 Socialstream is a package by Joel Butcher that provides a simple Socialite implementation for Laravel Jetstream.

Installing this package is a breeze, and it takes care of installing Jetstream under the hood if you’re starting a new application.

It replaces the published authentication and profile scaffolding provided by Jetstream with scaffolding that has support for Laravel Socialite one you install the package and run the install command:

1php artisan socialstream:install

The install command overwrites the published Jetstream files required for Socialstream to work within Jetstream. Using the built-in Socialite providers and the community Socialite Providers it’s a breeze to scaffold social authentication providers within Jetstream!

Out of the box, it enables GitHub (you will need to provide your app credentials):

You can configure them in the published config/socialstream.php file:

1return [
2    /*
3     | Supported: "google", "facebook", "github", "gitlab",
4     |            "bitbucket", "linkedin", "twitter"
5     */
6    'providers' => [
7        'github'
8    ],
9];

You can learn more about this package, get full installation instructions, and view the source code on GitHub.

Read More

Bandwagon is a Social Proof Package for Laravel

 Laravel Bandwagon is a package to help promote social proof and legitimacy within your application. You can let users of your application know when others’ share, purchase, subscribe, or donate, for example:

Using blade and Vue, here’s how easy it is to feed data into the social proof component, which is then displayed in the user’s browser via polling:

 1use Bndwgn\Bandwagon\Bandwagon;
 2 
 3public function purchase(Request $request, Product $product)
 4{
 5    $user = Auth::user();
 6    // ... logic to charge a customer
 7    Bandwagon::createEvent(
 8        "Someone from ${$user->state}",
 9        "Purchased the ${$product->displayName} plan",
10        $request->ip()
11    );
12}

In your blade template (i.e., on your product page), you render the widget by using the provided blade component:

1<x-bandwagon-renderer />

The package allows you to configure things like poll increments (how often to check for new events), how long to display events, and the age of valid events.

Bandwagon’s documentation is available on www.laravelbandwagon.com, and you can learn more about this package’s source code on GitHub.

Read More