feat: create configs

config/data.php

@@ -0,0 +1,195 @@
+<?php
+
+return [
+    /**
+     * The package will use this format when working with dates. If this option
+     * is an array, it will try to convert from the first format that works,
+     * and will serialize dates using the first format from the array.
+     */
+    'date_format' => DATE_ATOM,
+
+    /**
+     * When transforming or casting dates, the following timezone will be used to
+     * convert the date to the correct timezone. If set to null no timezone will
+     * be passed.
+     */
+    'date_timezone' => null,
+
+    /**
+     * It is possible to enable certain features of the package, these would otherwise
+     * be breaking changes, and thus they are disabled by default. In the next major
+     * version of the package, these features will be enabled by default.
+     */
+    'features' => [
+        'cast_and_transform_iterables' => false,
+
+        /**
+         * When trying to set a computed property value, the package will throw an exception.
+         * You can disable this behaviour by setting this option to true, which will then just
+         * ignore the value being passed into the computed property and recalculate it.
+         */
+        'ignore_exception_when_trying_to_set_computed_property_value' => false,
+    ],
+
+    /**
+     * Global transformers will take complex types and transform them into simple
+     * types.
+     */
+    'transformers' => [
+        DateTimeInterface::class => \Spatie\LaravelData\Transformers\DateTimeInterfaceTransformer::class,
+        \Illuminate\Contracts\Support\Arrayable::class => \Spatie\LaravelData\Transformers\ArrayableTransformer::class,
+        BackedEnum::class => Spatie\LaravelData\Transformers\EnumTransformer::class,
+    ],
+
+    /**
+     * Global casts will cast values into complex types when creating a data
+     * object from simple types.
+     */
+    'casts' => [
+        DateTimeInterface::class => Spatie\LaravelData\Casts\DateTimeInterfaceCast::class,
+        BackedEnum::class => Spatie\LaravelData\Casts\EnumCast::class,
+//        Enumerable::class => Spatie\LaravelData\Casts\EnumerableCast::class,
+    ],
+
+    /**
+     * Rule inferrers can be configured here. They will automatically add
+     * validation rules to properties of a data object based upon
+     * the type of the property.
+     */
+    'rule_inferrers' => [
+        Spatie\LaravelData\RuleInferrers\SometimesRuleInferrer::class,
+        Spatie\LaravelData\RuleInferrers\NullableRuleInferrer::class,
+        Spatie\LaravelData\RuleInferrers\RequiredRuleInferrer::class,
+        Spatie\LaravelData\RuleInferrers\BuiltInTypesRuleInferrer::class,
+        Spatie\LaravelData\RuleInferrers\AttributesRuleInferrer::class,
+    ],
+
+    /**
+     * Normalizers return an array representation of the payload, or null if
+     * it cannot normalize the payload. The normalizers below are used for
+     * every data object, unless overridden in a specific data object class.
+     */
+    'normalizers' => [
+        Spatie\LaravelData\Normalizers\ModelNormalizer::class,
+        // Spatie\LaravelData\Normalizers\FormRequestNormalizer::class,
+        Spatie\LaravelData\Normalizers\ArrayableNormalizer::class,
+        Spatie\LaravelData\Normalizers\ObjectNormalizer::class,
+        Spatie\LaravelData\Normalizers\ArrayNormalizer::class,
+        Spatie\LaravelData\Normalizers\JsonNormalizer::class,
+    ],
+
+    /**
+     * Data objects can be wrapped into a key like 'data' when used as a resource,
+     * this key can be set globally here for all data objects. You can pass in
+     * `null` if you want to disable wrapping.
+     */
+    'wrap' => null,
+
+    /**
+     * Adds a specific caster to the Symphony VarDumper component which hides
+     * some properties from data objects and collections when being dumped
+     * by `dump` or `dd`. Can be 'enabled', 'disabled' or 'development'
+     * which will only enable the caster locally.
+     */
+    'var_dumper_caster_mode' => 'development',
+
+    /**
+     * It is possible to skip the PHP reflection analysis of data objects
+     * when running in production. This will speed up the package. You
+     * can configure where data objects are stored and which cache
+     * store should be used.
+     *
+     * Structures are cached forever as they'll become stale when your
+     * application is deployed with changes. You can set a duration
+     * in seconds if you want the cache to clear after a certain
+     * timeframe.
+     */
+    'structure_caching' => [
+        'enabled' => true,
+        'directories' => [app_path('Data')],
+        'cache' => [
+            'store' => env('CACHE_STORE', env('CACHE_DRIVER', 'file')),
+            'prefix' => 'laravel-data',
+            'duration' => null,
+        ],
+        'reflection_discovery' => [
+            'enabled' => true,
+            'base_path' => base_path(),
+            'root_namespace' => null,
+        ],
+    ],
+
+    /**
+     * A data object can be validated when created using a factory or when calling the from
+     * method. By default, only when a request is passed the data is being validated. This
+     * behaviour can be changed to always validate or to completely disable validation.
+     */
+    'validation_strategy' => \Spatie\LaravelData\Support\Creation\ValidationStrategy::OnlyRequests->value,
+
+    /**
+     * A data object can map the names of its properties when transforming (output) or when
+     * creating (input). By default, the package will not map any names. You can set a
+     * global strategy here, or override it on a specific data object.
+     */
+    'name_mapping_strategy' => [
+        'input' => null,
+        'output' => null,
+    ],
+
+    /**
+     * When using an invalid include, exclude, only or except partial, the package will
+     * throw an exception. You can disable this behaviour by setting this option to true.
+     */
+    'ignore_invalid_partials' => false,
+
+    /**
+     * When transforming a nested chain of data objects, the package can end up in an infinite
+     * loop when including a recursive relationship. The max transformation depth can be
+     * set as a safety measure to prevent this from happening. When set to null, the
+     * package will not enforce a maximum depth.
+     */
+    'max_transformation_depth' => null,
+
+    /**
+     * When the maximum transformation depth is reached, the package will throw an exception.
+     * You can disable this behaviour by setting this option to true which will return an
+     * empty array.
+     */
+    'throw_when_max_transformation_depth_reached' => true,
+
+    /**
+    * When using the `make:data` command, the package will use these settings to generate
+    * the data classes. You can override these settings by passing options to the command.
+    */
+    'commands' => [
+        /**
+         * Provides default configuration for the `make:data` command. These settings can be overridden with options
+         * passed directly to the `make:data` command for generating single Data classes, or if not set they will
+         * automatically fall back to these defaults. See `php artisan make:data --help` for more information
+         */
+        'make' => [
+            /**
+             * The default namespace for generated Data classes. This exists under the application's root namespace,
+             * so the default 'Data` will end up as '\App\Data', and generated Data classes will be placed in the
+             * app/Data/ folder. Data classes can live anywhere, but this is where `make:data` will put them.
+             */
+            'namespace' => 'Data',
+
+            /**
+             * This suffix will be appended to all data classes generated by make:data, so that they are less likely
+             * to conflict with other related classes, controllers or models with a similar name without resorting
+             * to adding an alias for the Data object. Set to a blank string (not null) to disable.
+             */
+            'suffix' => 'Data',
+        ],
+    ],
+
+    /**
+     * When using Livewire, the package allows you to enable or disable the synths
+     * these synths will automatically handle the data objects and their
+     * properties when used in a Livewire component.
+     */
+    'livewire' => [
+        'enable_synths' => false,
+    ],
+];

config/sanctum.php

@@ -0,0 +1,83 @@
+<?php
+
+use Laravel\Sanctum\Sanctum;
+
+return [
+
+    /*
+    |--------------------------------------------------------------------------
+    | Stateful Domains
+    |--------------------------------------------------------------------------
+    |
+    | Requests from the following domains / hosts will receive stateful API
+    | authentication cookies. Typically, these should include your local
+    | and production domains which access your API via a frontend SPA.
+    |
+    */
+
+    'stateful' => explode(',', env('SANCTUM_STATEFUL_DOMAINS', sprintf(
+        '%s%s',
+        'localhost,localhost:3000,127.0.0.1,127.0.0.1:8000,::1',
+        Sanctum::currentApplicationUrlWithPort()
+    ))),
+
+    /*
+    |--------------------------------------------------------------------------
+    | Sanctum Guards
+    |--------------------------------------------------------------------------
+    |
+    | This array contains the authentication guards that will be checked when
+    | Sanctum is trying to authenticate a request. If none of these guards
+    | are able to authenticate the request, Sanctum will use the bearer
+    | token that's present on an incoming request for authentication.
+    |
+    */
+
+    'guard' => ['web'],
+
+    /*
+    |--------------------------------------------------------------------------
+    | Expiration Minutes
+    |--------------------------------------------------------------------------
+    |
+    | This value controls the number of minutes until an issued token will be
+    | considered expired. This will override any values set in the token's
+    | "expires_at" attribute, but first-party sessions are not affected.
+    |
+    */
+
+    'expiration' => null,
+
+    /*
+    |--------------------------------------------------------------------------
+    | Token Prefix
+    |--------------------------------------------------------------------------
+    |
+    | Sanctum can prefix new tokens in order to take advantage of numerous
+    | security scanning initiatives maintained by open source platforms
+    | that notify developers if they commit tokens into repositories.
+    |
+    | See: https://docs.github.com/en/code-security/secret-scanning/about-secret-scanning
+    |
+    */
+
+    'token_prefix' => env('SANCTUM_TOKEN_PREFIX', ''),
+
+    /*
+    |--------------------------------------------------------------------------
+    | Sanctum Middleware
+    |--------------------------------------------------------------------------
+    |
+    | When authenticating your first-party SPA with Sanctum you may need to
+    | customize some of the middleware Sanctum uses while processing the
+    | request. You may change the middleware listed below as required.
+    |
+    */
+
+    'middleware' => [
+        'authenticate_session' => Laravel\Sanctum\Http\Middleware\AuthenticateSession::class,
+        'encrypt_cookies' => Illuminate\Cookie\Middleware\EncryptCookies::class,
+        'validate_csrf_token' => Illuminate\Foundation\Http\Middleware\ValidateCsrfToken::class,
+    ],
+
+];