README

Allow a User to block another User. Blocking a User will prevent the blocker from seeing the blockees data.

Installation

You can install the package via composer:

composer require cjmellor/blockade

You can publish and run the migrations with:

php artisan vendor:publish --tag="blockade-migrations"

php artisan migrate

and publish the config file with:

php artisan vendor:publish --tag="blockade-config"

This is the contents of the published config file:

return [
    /**
     * If your User model different to the default, you can specify it here.
     */
    'user_model' => 'App\Models\User',
    
    /**
     * Specify the user model's foreign key.
     */
    'user_foreign_key' => 'user_id',

    /**
     * Specify the table name for the blocks table.
     */
    'blocks_table' => 'blocks',

    /**
     * Specify the foreign key for the blocker.
     */
    'blocker_foreign_key' => 'blocker_id',

    /**
     * Specify the foreign key for the blocked.
     */
    'blocked_foreign_key' => 'blocked_id',

    /**
     * Schedule the cleanup of expired blocks.
     */
    'schedule_cleanup' => false,
];

Usage

Using the Traits

CanBlock

Add the CanBlock trait to your User model.

This trait should only ever be added to your User model.

use Cjmellor\Blockade\Concerns\CanBlock;

class User
{
    use CanBlock;
    
    // ...
}

HasBlocked

Use this trait in your Models where you would not want a User to see the Model of a User they have blocked.

Example: you have a Comment Model and User 7 has blocked User 8 so User 7 should not be able to see any comments made by User 8.

use Cjmellor\Blockade\Concerns\HasBlocked;

class Comment
{
    use HasBlocked;
    
    // ...
}

Block a User

A User can block another User by supplying a User model, or just the ID of the User to be blocked.

$user->block(User::find(2)));

// or

$user->block(2);

Note: You cannot block yourself.

Unblock a User

A User can unblock another User by supplying a User model, or just the ID of the User to be unblocked.

$user->unblock(User::find(2)));

// or

$user->unblock(2);

Checking if a User is blocked

You can run a check to see if you're already blocking a User or not.

$user->isBlocking(User::find(2)));

// or

$user->isBlocking(2);

Set a block expiry

You can set an expiry date when blocking a User. This will automatically unblock the User after the expiry date has passed.

$user->block(User::find(2), expiresAt: now()->addDays(7)));

This example will block the User for 7 days. After 7 days, the User will be unblocked.

⏱️ Scheduling the cleanup of expired blocks

By default, a blocked User with an expiry will not be removed after the expiry time as past.

If you want to automatically remove expired blocks, you can set the schedule_cleanup config value in the config/blockade config file to true.

If you want more control over when the cleanup is run, there is an artisan command that can be run to remove expired blocks.

php artisan unblock:expired

You can also schedule this command to run automatically.

$schedule->command('unblock:expired')->everyMinute();

Note

Don't forget to add the command to the App\Console\Kernel schedule() method.

Events

When a User is blocked, a UserBlocked event is fired.

When a User is unblocked, a UserUnblocked event is fired.

The User Model of the blocked or unblocked User is passed to the event so you can listen for these events and perform further actions.

Testing

composer test

Changelog

Please see CHANGELOG for more information on what has changed recently.

License

The MIT License (MIT). Please see License File for more information.

cjmellor / blockade

Maintainers

Details