Download the PHP package zvermafia/larastate without Composer

Larastate — a main source for your entity states values

Easy access to entity states values and to their localizations.

Navigation by sections

• Introduction
  • The problem
  • A solution
• Install
• Setup
• Usage
• Alternatives
• Change log
• Contributing
• Security
• Credits
• License

Introduction

The problem

When you have an entity with some states you usually need to access to those states' values and to their localizations. Let's consider the following cases:

Let's assume we have a User entity with a role state. And the role state can only accept 'member', 'moderator' and 'administrator' values.

• When you need to validate a state's acceptable values. So when we try to create a new user we need to validate the role state value. But how to do it if we don't have a main source for that values? And usually we may do like below:

• When you need to display localization for one of the state's values. For example when you need to give an information about a user's role:

  🙁 Localization file path, file name and locale key are hardcoded.

• When you need to display those values with locales. For example in a select box:

  🙁 Hardcoded, hardcoded, ...

And yes when you hardcoded those values in different places of your project then it will be harder to change (add, remove, rename) those values. Because you don't use a main source for those values.

A solution

Unfortunately Laravel doesn't provide a solution for this problem out of the box. So I've created this package. With this package you will not have problems in the above section! Let's solve those problems in the appropriate order.

Firstly create a States folder in the app directory, then create a UserState class in it with extending a StateAbstract abstract class. And define a ROLE constant in the class with those values from the above section. You should have something below:

• When you need to validate a state's acceptable values:

• When you need to display localization for one of the state's values. For example when you need to give an information about a user's role:

  🙂 Localization file path, file name and locale key are taken from the single source!

• When you need to display those values with locales. For example in a select box:

  🙂 Much better!

Install

To install the package just pull it via composer and you're ready to setup.

Setup

The package have some convention about structuring a state classes directory, naming those classes and naming constants. But all this can be changed to suit your needs by extending a StateAbstract abstract class. So if you need it then take a look at the source code.

• By default you should put all your state classes to app/States directory. And yes usually there is not that directory so you need to create it by yourself.
• And your state class names should end with State postfix, for example UserState, PageState, OrderState and so on...
• Constant names should be in upper case and each word separated by underscore.

Let's assume we want to setup a state class for a post entity, so our steps are follows:

1. Create a States folder in the app directory;
2. Create a PostState.php file and put it into the app/States directory;

3. Extend a StateAbstract abstract class and define constants, you should have something below:

4. Create localization file in a resources/lang/en/entities directory with the entity name, so in our case it will be post.php . It's a regular Laravel's localization file but by default all state localizations should be grouped in a state key of the array. So you should have something like below:

Usage

For usage example we will use our PostState which we created it in the above section.

There are three cases and all works through PHP's magic __call() method:

1. Getting values for the state
2. Getting values with locales for the state
3. Getting a locale for one of the state's values

All methods start with prefix get and ends with one of the case names (Values, ValuesWithLocales or Locale). And between those prefix and postfixes you should write your state name in StudlyCase format.

For a type state those will be:

1. getTypeValues()
2. getTypeValuesWithLocales()
3. getTypeLocale(1)

Alternatives

• BenSampo/laravel-enum
• artkonekt/enum-eloquent
• nasyrov/laravel-enums
• mad-web/laravel-enum
• spatie/laravel-enum
• cerbero90/laravel-enum

So why I've created this package when there is already such kind of packages? Because they are a bit complicated for my simple task.

Change log

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

Testing

Contributing

Please see CODE_OF_CONDUCT for details.

Security

If you discover any security related issues, please email [email protected] instead of using the issue tracker.

Credits

• Mokhirjon Naimov
• All Contributors

License

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