BinarCode
diff --git a/‎README.md‎
Lines changed: 6 additions & 2 deletions b/‎README.md‎
Lines changed: 6 additions & 2 deletions
diff --git a/‎UPGRADING.md‎
Lines changed: 7 additions & 0 deletions b/‎UPGRADING.md‎
Lines changed: 7 additions & 0 deletions
diff --git a/‎config/restify.php‎
Lines changed: 13 additions & 1 deletion b/‎config/restify.php‎
Lines changed: 13 additions & 1 deletion
diff --git a/‎docs-v2/content/en/api/actions.md‎
Lines changed: 31 additions & 31 deletions b/‎docs-v2/content/en/api/actions.md‎
Lines changed: 31 additions & 31 deletions
@@ -23,6 +23,10 @@ You can install the package via composer:
 composer require binaryk/laravel-restify
 ```
 
+## Playground
+
+You can find a playground in the [Restify Demo GitHub repository](https://github.com/BinarCode/restify-demo).
+
 ## Videos
 
 If you are a visual learner, checkout [our video course](https://www.binarcode.com/learn/restify) for the Laravel Restify.
@@ -87,11 +91,11 @@ Please see [CONTRIBUTING](CONTRIBUTING.md) for details.
 
 ### Security
 
-If you discover any security related issues, please email eduard.lupacescu@binarcode.com instead of using the issue tracker.
+If you discover any security related issues, please email eduard.lupacescu@binarcode.com or [message me on twitter](https://twitter.com/LupacescuEuard) instead of using the issue tracker.
 
 ## Credits
 
-- [Eduard Lupacescu](https://github.com/binaryk)
+- [Eduard Lupacescu](https://twitter.com/LupacescuEuard)
 - [Koen Koenster](https://github.com/Koenster)
 - [All Contributors](../../contributors)
 
 
@@ -1,5 +1,11 @@
 # Upgrading
 
+## From 7.3.1 to 7.4.0
+
+## Breaking
+
+- The `$eagerState` repository property is now private, and it is of type `null|string` because it holds the parent repository that renders it.
+
 ## From 6.x to 7.x
 
 High impact:
@@ -13,6 +19,7 @@ High impact:
     - `$defaultPerPage` and `$defaultRelatablePerPage` has a type of `int`, if you override this make sure you add `int` type
     - `eagerState` method was deleted from the repository, there is no need to call it anymore, the repository will be resolved automatically
     - `$prefix` property requires a `string` type
+    - `resolveShowMeta` is not inherited for the `resolveIndexMeta` anymore, both methods are now using `policyMeta` method, so override the `policyMeta` instead. This could be simply solved if you replace in all repositories `resolveShowMeta` with `policyMeta`.
 - Relations that are present into `include` or `related` will be preloaded, so if you didn't specify a repository to serialize the related relationship, and you're looking for the Eloquent to resolve it, it will not invoke the `restify.casts.related` cast anymore, instead it'll load the relationship as it. This has a performance reason under the hood. 
 - Since related relationships will be preloaded, the format of the belongs to will be changed now. If you didn't specify the repository to serialize the `belongsTo` relationship, it'll be serialized as an object, not array anymore:
 
 
@@ -136,7 +136,7 @@
 
     'repositories' => [
         /*
-        | Specify either to serialize index meta (policy) information or not. For performance reasons we recommend to disable it.
+        | Specify either to serialize index meta (policy) information or not. For performance reasons we recommend disabling it.
         */
         'serialize_index_meta' => false,
 
@@ -145,4 +145,16 @@
         */
         'serialize_show_meta' => true,
     ],
+
+    'cache' => [
+        /*
+        | Specify the cache configuration for the resources policies.
+        | When enabled, methods from the policy will be cached for the active user.
+        */
+        'policies' => [
+            'enabled' => false,
+
+            'ttl' => 5 * 60, // seconds
+        ],
+    ],
 ];
@@ -7,9 +7,9 @@ position: 9
 
 ## Motivation
 
-Besides, built in CRUD operations and filtering, Restify allows you to define extra actions for your repositories.
+Built in CRUD operations and filtering, Restify allows you to define extra actions for your repositories.
 
-Let's say you have a list of posts, and you have to publish them. Usually for this kind of operations, you have to define a custom route like:
+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
 $router->post('posts/publish', PublishPostsController::class);
@@ -18,19 +18,19 @@ $router->post('posts/publish', PublishPostsController::class);
 
 public function __invoke(RestifyRequest $request)
 {
-  ...
+  //...
 }
 ```
 
-The `classic` approach is good, however, it has a few limitations. Firstly, you have to manually take care of the route `middleware`, the testability for these endpoints should be done separately which is hard to maintain. And finally, the endpoint is disconnected from the repository, which makes it feel out of context so has a bad readability.
+The `classic` approach is good. However, it has a few limitations. First, you have to manually take care of the `middleware` route, as the testability for these endpoints should be done separately, which might be hard to maintain. Ultimately, the endpoint is disconnected from the repository, which makes it feel out of context so it has a bad readability.
 
-So, code readability, testability and maintainability become hard.
+On that wise, code readability, testability and maintainability may become hard.
 
 ## Action definition
 
-The action is nothing more than a class, that extends the `Binaryk\LaravelRestify\Actions\Action` abstract class.
+The action is nothing more than a class that extends the `Binaryk\LaravelRestify\Actions\Action` abstract class.
 
-It could be generated by using the command:
+It could be generated by using the following command:
 
 ```bash
 php artisan restify:action PublishPostsAction
@@ -98,7 +98,7 @@ POST: api/restify/posts/actions?action=publish-posts-action
 The `action` query param value is the `ke-bab` form of the filter class name by default, or a custom `$uriKey` [defined in the action](#custom-uri-key)
 
 
-The payload could be any type of json data, however, if you're using an [index-action](#index-actions), you are required to pass the `repositories` key, which represents the list of model keys we apply the action:
+The payload could be any type of json data. However, if you're using an [index-action](#index-actions), you are required to pass the `repositories` key, which represents the list of model keys that we apply to this action:
 
 ```json
 {
@@ -108,7 +108,7 @@ The payload could be any type of json data, however, if you're using an [index-a
 
 ### Handle action
 
-As soon the action is called, the handled method will be invoked with the `$request` and list of models matching the keys passed via `repositories`:
+As soon the action is called, the handled method will be invoked with the `$request` and a list of models matching the keys passed via `repositories`:
 
 ```php
 public function handle(ActionRequest $request, Collection $models)
@@ -121,7 +121,7 @@ public function handle(ActionRequest $request, Collection $models)
 
 ## Action customizations
 
-Actions could be easily customized.
+Actions can be easily customized.
 
 ### Action index query
 
@@ -143,7 +143,7 @@ This method will be called right before items are retrieved from the database, s
 
 ### Custom uri key
 
-Since your class names could change along the way, you can define a `$uriKey` property to your actions, so the frontend will use always the same `action` query when applying an action:
+Since your class names might change along the way, you can define a `$uriKey` property to your actions, so the frontend will always use the same `action` query when applying an action:
 
 ```php
 class PublishPostAction extends Action
@@ -169,7 +169,7 @@ public function rules(): array
 ```
 
 <alert type="danger">
-Restify doesn't validate the payload automatically as it does for filters, you're free to validate the payload in the handle method.
+Restify doesn't validate the payload automatically as it does for filters, so you're free to validate the payload in the handle method.
 </alert>
 
 Always validate the payload as early as possible in the `handle` method:
@@ -190,13 +190,13 @@ By default, any action could be used on [index](#index-actions) as well as on [s
 
 ## Show actions
 
-Show actions are used when you have to apply it for a single item.
+Show actions are used when you have to apply them for a single item.
 
 ### Show action definition
 
-The show action definition is different in the way it receives arguments for the `handle` method. 
+The show action definition is different, in a way it receives arguments for the `handle` method. 
 
-Restify automatically resolves Eloquent models defined in the route id and passes it to the action's handle method:
+Restify automatically resolves Eloquent models defined in the route id and passes them to the action's handle method:
 
 ```php
 // PublishPostAction.php
@@ -247,13 +247,13 @@ See [get available actions](#get-available-actions) for more details.
 
 ## Index actions
 
-Index actions are used when you have to apply it for a many items.
+Index actions are used when you have to apply them for a many items.
 
 ### Index action definition
 
 The index action definition is different in the way it receives arguments for the `handle` method. 
 
-Restify automatically resolves Eloquent models sent via the `repositories` key sent into the call payload and passes it to the action's handle method as a collection of items:
+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
@@ -289,7 +289,7 @@ The post URL:
 POST: api/restfiy/posts/actions?action=publish-posts-action
 ```
 
-The payload should always include a key called `repositories`, which is an array of model keys or the `all` keyword if you want to get all:
+The payload should always include a key called `repositories`, which is an array of model keys or the `all` keyword if you want to get them all:
 
 ```json
 {
@@ -301,7 +301,7 @@ So Restify will resolve posts with ids in the list of `[1, 2, 3]`.
 
 ### Apply index action for all
 
-You can apply the index action for all models from the database if you send the payload: 
+You can apply the index action for all the models from the database if you send the payload: 
 
 ```json
 {
@@ -331,12 +331,12 @@ See [get available actions](#get-available-actions) for more details.
 
 ## Standalone actions
 
-Sometimes you don't need to have an action with models. Let's say for example the authenticated user wants to disable
-his account. 
+Sometimes, you don't need to have an action with models. Let's say for example the authenticated user wants to disable
+his/her account. 
 
 ### Standalone action definition:
 
-The index action definition is different in the way it doesn't require the second argument for the `handle`.
+The index action definition is different, in a way it doesn't require the second argument for the `handle`.
 
 ```php
 // DisableProfileAction.php
@@ -401,14 +401,14 @@ sending.
 
 ## Action Log
 
-It is often useful to view a log of the actions that have been run against a model, or seeing when the model was
+Oftentimes, it is quite useful to view a log of the actions that have been run against a model, or see when the model was
 updated, deleted or created (and by whom). 
 
-Thankfully, Restify makes it a breeze to add an action log to a model by attaching the `Binaryk\LaravelRestify\Models\Concerns\HasActionLogs`  trait to the repository's corresponding Eloquent model.
+Thankfully, Restify makes it a breeze to add an action log to a model by attaching the `Binaryk\LaravelRestify\Models\Concerns\HasActionLogs` trait to the repository's corresponding Eloquent model.
 
 ### Activate logs
 
-Simply adding the `HasActionLogs` trait to your model, it will log all actions and CRUD operations into the database into the `action_logs` table:
+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
@@ -421,7 +421,7 @@ class Post extends Model
 
 ### Display logs
 
-You can display them by attaching to the repository related for example:
+You can display them by attaching them to the related repository for example:
 
 ```php
 // PostRepository.php
@@ -436,7 +436,7 @@ public static function related(): array
 }
 ```
 
-So now you can call the posts with logs `api/restify/posts/1?related=logs`, and it will return you the list of actions
+Now you can call the posts with logs `api/restify/posts/1?related=logs`, and it will return you the list of actions
 performed for posts:
 
 ```json
@@ -460,7 +460,7 @@ performed for posts:
 
 ### Custom logs repository
 
-Definitely you can use your own `ActionLogRepository`. Just ensure you define it into the config: 
+You can definitely use your own `ActionLogRepository`. Just make sure you have it defined into the config: 
 
 ```php
 // config/restify.php
@@ -472,7 +472,7 @@ Definitely you can use your own `ActionLogRepository`. Just ensure you define it
 
 ## Get available actions
 
-The frontend which consume your API could check available actions by using exposed endpoint:
+The frontend that consumes your API could check available actions by using this exposed endpoint:
 
 ```http request
 GET: api/api/restify/posts/actions
@@ -493,9 +493,9 @@ This will answer with a json like:
 
 `name` - humanized name of the action
 
-`destructive` - you may extend the `Binaryk\LaravelRestify\Actions\DestructiveAction` to indicate to the frontend than
+`destructive` - you may extend the `Binaryk\LaravelRestify\Actions\DestructiveAction` to indicate to the frontend that
 this action is destructive (could be used for deletions)
 
-`uriKey` - is the key of the action, will be used to perform the action
+`uriKey` - is the key of the action and it will be used to perform the action
 
 `payload` - a key / value object indicating required payload defined in the `rules` Action class