From 2121af291413fe77e54940cf585cf6ed42ac2c0e Mon Sep 17 00:00:00 2001
From: Leonid Nikitin <i@kor-elf.net>
Date: Wed, 12 Jul 2023 22:30:05 +0600
Subject: [PATCH] Renamed the "slug" field in the roles table to "code" to
 facilitate coding standards and improve readability. This unique identifier
 will now be referred to as 'code' across the application, creating
 consistency and reducing potential confusion in the future.

!!! Since the project has not yet been launched, therefore, I do not create a new migration, but change the current one. !!!
---
 database/migrations/2023_06_28_155124_create_roles.php | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/database/migrations/2023_06_28_155124_create_roles.php b/database/migrations/2023_06_28_155124_create_roles.php
index ed1d755..94ad89f 100644
--- a/database/migrations/2023_06_28_155124_create_roles.php
+++ b/database/migrations/2023_06_28_155124_create_roles.php
@@ -18,14 +18,14 @@ return new class extends Migration
         Schema::create('roles', function (Blueprint $table) {
             $table->id();
             $table->string('name');
-            $table->string('slug')->unique();
+            $table->string('code')->unique();
             $table->timestamps();
             $table->softDeletes();
         });
 
         DB::table('roles')->insert([
             'name' => 'Administrator',
-            'slug' => 'admin',
+            'code' => 'admin',
             'created_at' => Carbon::now(),
             'updated_at' => Carbon::now()
         ]);