refactor: update code snippets in documentation for clarity and consistency

Author: denisdobra10

docs-v3/.data/content/contents.sqlite

@@ -0,0 +1,65 @@
+<template>
+  <div :class="ui.root({ class: [props.ui?.root], filename: !!filename })">
+    <div v-if="filename && !hideHeader" :class="ui.header({ class: props.ui?.header })">
+      <span 
+        v-if="language === 'php'" 
+        class="inline-flex items-center justify-center h-5 px-1.5 text-xs font-bold text-blue-700 dark:text-blue-200 bg-blue-100 dark:bg-blue-900/30 rounded border border-blue-300 dark:border-blue-700"
+      >
+        PHP
+      </span>
+      <UIcon v-else :name="icon || getFileTypeIcon(filename)" :class="ui.icon({ class: props.ui?.icon })" />
+
+      <span :class="ui.filename({ class: props.ui?.filename })">{{ filename }}</span>
+    </div>
+
+    <UButton
+      :icon="copied ? appConfig.ui.icons.copyCheck : appConfig.ui.icons.copy"
+      color="neutral"
+      variant="outline"
+      size="sm"
+      :aria-label="copied ? 'Copied!' : 'Copy'"
+      :label="copied ? 'Copied' : 'Copy'"
+      :class="ui.copy({ class: props.ui?.copy })"
+      tabindex="-1"
+      @click="copyCode"
+    />
+
+    <pre :class="ui.base({ class: [props.ui?.base, props.class] })" v-bind="$attrs"><slot /></pre>
+  </div>
+</template>
+
+<script setup>
+import theme from "#build/ui/prose/pre";
+import { computed } from "vue";
+import { useClipboard } from "@vueuse/core";
+import { useAppConfig } from "#imports";
+import { tv } from "tailwind-variants";
+
+const props = defineProps({
+  icon: { type: [String, Object], required: false },
+  code: { type: String, required: false },
+  language: { type: String, required: false },
+  filename: { type: String, required: false },
+  hideHeader: { type: Boolean, required: false },
+  class: { type: null, required: false },
+  ui: { type: null, required: false }
+});
+defineSlots();
+
+const { copy, copied } = useClipboard();
+const appConfig = useAppConfig();
+const ui = computed(() => tv({ extend: tv(theme), ...appConfig.ui?.prose?.pre || {} })());
+
+const getFileTypeIcon = (filename) => {
+  if (!filename) return null;
+  
+  const cleanFilename = filename.replace(/\s*\(.*\)\s*$/, "");
+  const extension = cleanFilename.includes(".") && cleanFilename.split(".").pop();
+  
+  return extension ? `i-vscode-icons-file-type-${extension}` : null;
+};
+
+const copyCode = async () => {
+  await copy(props.code || '');
+};
+</script>

docs-v3/components/content/ProsePre.vue

@@ -11,11 +11,9 @@ Built in CRUD operations and filtering, Restify allows you to define extra actio
 
 Let's say you have a list of posts and you have to publish them. Usually, for these kind of operations, you have to define a custom route like:
 
-```php
+```php [PublishPostsController.php]
 $router->post('posts/publish', PublishPostsController::class);
 
-// PublishPostsController.php
-
 public function __invoke(RestifyRequest $request)
 {
   //...
@@ -100,9 +98,7 @@ The `$models` argument represents a collection of all the models for this query.
 
 Then add the action instance to the repository `actions` method:
 
-```php
-// PostRepository.php
-
+```php [PostRepository.php]
 public function actions(RestifyRequest $request): array
 {
     return [
@@ -294,9 +290,7 @@ The show action definition is different, in a way it receives arguments for the
 
 Restify automatically resolves Eloquent models defined in the route id and passes them to the action's handle method:
 
-```php
-// PublishPostAction.php
-
+```php [PublishPostAction.php]
 public function handle(ActionRequest $request, Post $post): JsonResponse
 {
 
@@ -351,8 +345,7 @@ The index action definition is different in the way it receives arguments for th
 
 Restify automatically resolves Eloquent models sent via the `repositories` key into the call payload. Then, it passes it to the action's handle method as a collection of items:
 
-```php
-// PublishPostAction.php
+```php [PublishPostAction.php]
 use Illuminate\Support\Collection;
 
 public function handle(ActionRequest $request, Collection $posts): JsonResponse
@@ -366,9 +359,7 @@ public function handle(ActionRequest $request, Collection $posts): JsonResponse
 
 To register an index action, we have to use the `->onlyOnIndex()` accessor:
 
-```php
-// PostRepository.php
-
+```php [PostRepository.php]
 public function actions(RestifyRequest $request)
 {
     return [
@@ -409,9 +400,7 @@ Restify will get chunks of 200 and send them into the `Collection` argument for
 
 You can customize the chunk number by customizing the `chunkCount` action property:
 
-```php
-// PublishPostAction.php
-
+```php [PublishPostAction.php]
 public static int $chunkCount = 500;
 ```
 
@@ -434,9 +423,7 @@ his/her account.
 
 The index action definition is different, in a way it doesn't require the second argument for the `handle`.
 
-```php
-// DisableProfileAction.php
-
+```php [DisableProfileAction.php]
 public function handle(ActionRequest $request): JsonResponse
 {
     //
@@ -448,9 +435,7 @@ public function handle(ActionRequest $request): JsonResponse
 
 There are two ways to register the standalone action:
 
-```php
-// UserRepository
-
+```php [UserRepository]
 public function actions(RestifyRequest $request)
 {
     return [
@@ -506,9 +491,7 @@ Thankfully, Restify makes it a breeze to add an action log to a model by attachi
 
 By simply adding the `HasActionLogs` trait to your model, it will log all actions and CRUD operations into the database into the `action_logs` table:
 
-```php
-// Post.php
-
+```php [Post.php]
 class Post extends Model 
 {
     use \Binaryk\LaravelRestify\Models\Concerns\HasActionLogs;
@@ -519,8 +502,7 @@ class Post extends Model
 
 You can display them by attaching them to the related repository for example:
 
-```php
-// PostRepository.php
+```php [PostRepository.php]
 use Binaryk\LaravelRestify\Fields\MorphToMany;
 use Binaryk\LaravelRestify\Repositories\ActionLogRepository;
 
@@ -558,8 +540,7 @@ performed for posts:
 
 You can definitely use your own `ActionLogRepository`. Just make sure you have it defined into the config: 
 
-```php
-// config/restify.php
+```php [config/restify.php]
 ...
 'logs' => [
     'repository' => MyCustomLogsRepository::class,

docs-v3/content/docs/api/actions.md

@@ -18,7 +18,6 @@ using their static `new` or `make` method.
 The first argument is always the attribute name and usually matches the database `column`.
 
 ```php
-
 use Illuminate\Support\Facades\Hash;
 use Binaryk\LaravelRestify\Fields\Field;
 use Binaryk\LaravelRestify\Http\Requests\RestifyRequest;

docs-v3/content/docs/api/fields.md

@@ -93,9 +93,7 @@ class StripeInformationGetter extends Getter
 
 Then add the getter instance to the repository `getters` method:
 
-```php
-// UserRepository.php
-
+```php [UserRepository.php]
 public function getters(RestifyRequest $request): array
 {
     return [

docs-v3/content/docs/api/getters.md

@@ -75,8 +75,7 @@ Above we can see a few types of relationships declarations that Restify provides
 
 This means that there is a relationship of the `hasMany` type declared in the Company model. The Eloquent relationship name is `users` (see the first argument of the HasMany field): 
 
-```php
-// app/Models/Company.php
+```php [app/Models/Company.php]
 public function users(): \Illuminate\Database\Eloquent\Relations\HasMany
 {
     return $this->hasMany(User::class);
@@ -270,9 +269,7 @@ public static function related(): array
 
 The model should define the relationship `user`: 
 
-```php
-// Post.php
-
+```php [Post.php]
 public function user()
 {
     return $this->belongsTo(User::class);
@@ -610,9 +607,7 @@ You have a few options to authorize the `attach` endpoint.
 
 First, you can define the policy method `attachUsers`. The name should start with `attach` and suffix with the `CamelCase` name of the model's relationship name: 
 
-```php
-// CompanyPolicy.php
-
+```php [CompanyPolicy.php]
 public function attachUsers(User $authenticatedUser, Company $company, User $userToBeAttached): bool
 { 
     return $authenticatedUser->isAdmin();
@@ -691,9 +686,7 @@ $role->permissions()->sync($request->input('permissions'));
 
 You can define a policy method `syncPermissions`. The name should start with `sync` and suffix with the plural `CamelCase` name of the model's relationship name:
 
-```php
-// RolePolicy.php
-
+```php [RolePolicy.php]
 public function syncPermissions(User $authenticatedUser, Company $company, Collection $keys): bool
 { 
     // $keys are the primary keys of the related model (permissions in our case) Restify is trying to `sync`
@@ -722,9 +715,7 @@ You have a few options to authorize the `detach` endpoint.
 
 Primarily, you can define the policy method `detachUsers`, as the name should start with `detach` and suffix with the `CamelCase` name of the model relationship name:
 
-```php
-// CompanyPolicy.php
-
+```php [CompanyPolicy.php]
 public function detachUsers(User $authenticatedUser, Company $company, User $userToBeDetached): bool
 { 
     return $authenticatedUser->isAdmin();

docs-v3/content/docs/api/relations.md

@@ -161,8 +161,7 @@ class PostRepository extends Repository
 
 The default prefix of all Restify routes (except `login` and `register`) lives under the `restify->base` config:
 
-```php
-// config/restify.php
+```php [config/restify.php]
 ...
 'base' => '/api/restify',
 ...
@@ -183,8 +182,7 @@ GET: /api/restify/users
 
 However, you can prefix the repository with your own:
 
-```php
-// UserRepository
+```php [UserRepository]
 public static $prefix = 'api/v1';
 ```
 
@@ -206,8 +204,7 @@ will be used for all the endpoints related to the user repository.
 Each repository has the middlewares from the config `restify.middleware` out of the box for the CRUD methods. However,
 you're free to add your own middlewares for a specific repository.
 
-```php
-    // PostRepository.php
+```php [PostRepository.php]
 
     public static $middleware = [
         NeedsCompanyMiddleware::class,
@@ -629,8 +626,7 @@ class PostRepository extends Repository
 
 **1. Update your global gate to allow null users:**
 
-```php
-// app/Providers/RestifyApplicationServiceProvider.php
+```php [app/Providers/RestifyApplicationServiceProvider.php]
 protected function gate(): void
 {
     Gate::define('viewRestify', function ($user = null) {
@@ -645,8 +641,7 @@ protected function gate(): void
 
 **2. Update your policies to allow null users:**
 
-```php
-// app/Policies/PostPolicy.php
+```php [app/Policies/PostPolicy.php]
 public function allowRestify(User $user = null): bool
 {
     return true; // Allow all users (authenticated or not)
@@ -864,8 +859,7 @@ class PostRepository extends Repository
 
 Each repository has several lifecycle methods. The most useful is `booted`, which is called as soon as the repository is loaded:
 
-```php
-// PostRepository.php
+```php [PostRepository.php]
 protected static function booted()
 {
     // Initialization logic here

docs-v3/content/docs/api/repositories-advanced.md

@@ -288,8 +288,7 @@ GET /api/restify/posts?page=2&perPage=10
 
 Protect your repositories with Laravel policies:
 
-```php
-// app/Policies/PostPolicy.php
+```php [app/Policies/PostPolicy.php]
 class PostPolicy
 {
     public function allowRestify(User $user = null): bool