rennokki / eloquent-settings
Eloquent Settings allows you to bind key-value pairs to any Laravel Eloquent model. It supports even casting for boolean, float or integer types.
Fund package maintenance!
rennokki
Installs: 4 150
Dependents: 0
Suggesters: 0
Security: 0
Stars: 80
Watchers: 4
Forks: 5
Open Issues: 3
Requires
- illuminate/database: ^8.83|^9.0.1
- illuminate/support: ^8.83|^9.0.1
Requires (Dev)
- doctrine/dbal: ^2.8|^3.0
- laravel/legacy-factories: ^1.3
- mockery/mockery: ^1.5
- orchestra/database: ^6.28|^7.0
- orchestra/testbench: ^6.28|^7.0
- orchestra/testbench-core: ^6.28|^7.0
- phpunit/phpunit: ^9.5.13
- dev-master
- 5.1.0
- 5.0.0
- 4.7.0
- 4.6.1
- 4.6.0
- 4.5.0
- 4.4.1
- 4.4.0
- 4.3.1
- 4.3.0
- 4.2.0
- 4.1.0
- 4.0.1
- 4.0.0
- 3.0.0
- 2.3.3
- 2.3.2
- 2.3.1
- 2.3.0
- 2.2.0
- 2.1.0
- 2.0.0
- 1.3.0
- 1.2.3
- 1.2.2
- 1.2.1
- 1.2.0
- 1.1.0
- 1.0.0
- dev-dependabot/github_actions/codecov/codecov-action-4.2.0
- dev-dependabot/github_actions/actions/cache-4.0.2
- dev-dependabot/composer/laravel/legacy-factories-tw-1.4
This package is auto-updated.
Last update: 2024-08-09 00:05:56 UTC
README
Eloquent Settings allows you to bind key-value pairs to any Laravel Eloquent model.
🤝 Supporting
If you are using one or more Renoki Co. open-source packages in your production apps, in presentation demos, hobby projects, school projects or so, sponsor our work with Github Sponsors. 📦
🚀 Installation
Install the package:
$ composer require rennokki/eloquent-settings
Publish the config:
$ php artisan vendor:publish --provider="Rennokki\Settings\SettingsServiceProvider" --tag="config"
Publish the migrations:
$ php artisan vendor:publish --provider="Rennokki\Settings\SettingsServiceProvider" --tag="migrations"
🙌 Usage
You can add the HasSettings
trait to any Eloquent model:
use Rennokki\Settings\Traits\HasSettings; class User extends Model { use HasSettings; ... }
Adding settings
$user->newSetting('subscribed.to.newsletter', 1); $user->newSetting('subscribed.to.newsletter', true);
By default, settings' values are stored as string
. Later, if you try to get them with cast, they will return the value you have initially stored.
If you store 'true' as a string, if you cast it to a boolean, you'll get true
.
If you plan to store it with cast type other than string
, you can pass an additional third parameter that can be either string
, boolean
, bool
, int
, integer
, float
or double
.
$user->newSetting('subscribed.to.newsletter', true, 'bool');
Updating settings
Updating settings can be either to values, cast types or both, depending on what has changed.
$user->updateSetting('subscribed.to.newsletter', false, 'bool');
If you don't specify a cast parameter, it will not change, only the value will change, or viceversa.
Getting settings & values
You can get the Setting instance, not the value using getSetting()
:
$user->getSetting('subscribed.to.newsletter'); // does not accept a cast
If you plan to get the value, you can use getSettingValue()
:
$user->getSettingValue('subscribed.to.newsletter'); // true, as boolean $user->getSettingValue('subscribed.to.newsletter', 'int'); // 1, as integer
Remember, when you update or create a new setting, the cast type is stored. By default, next time you don't have to call the cast parameter again because it will cast it the way it was specified on storing.
$user->newSetting('is.cool', true, 'bool'); $user->getSettingValue('is.cool'); // it returns true as boolean
Getting values of not-known settings keys, you will return null
.
$user->getSettingValue('subscribed.to.weekly.newsletter'); // null
Deleting a setting
Deleting settings from the database can be done using deleteSetting()
.
$user->deleteSetting('subscribed.to.newsletter');
To delete all settings, call deleteSettings()
.
$user->deleteSettings();
🐛 Testing
vendor/bin/phpunit
🤝 Contributing
Please see CONTRIBUTING for details.
🔒 Security
If you discover any security related issues, please email alex@renoki.org instead of using the issue tracker.