Download the PHP package baethon/laravel-resource without Composer
On this page you can find all versions of the php package baethon/laravel-resource. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package laravel-resource
baethon/laravel-resource
The package provides a convenient factory function for Laravel API Resources. Based on the given model, it will try to find the corresponding API resource and return it. If the resource doesn't exist, it will use the base JsonResource class. It works with collections.
Installation
Example usage
Factory will work also with conditional loads:
How it works?
The package tries to follow the Laravels naming conventions. When creating a resource for User model, it will look for UserResource. When passing a collection of User instances, it will look for UserResourceCollection or UserCollection.
In the case of collections, the package won't wrap individual models in their respective resources. It will pass that responsibility to the collection resource instead.
Rationale
When you decide to use API resources, you should create an individual resource for each model returned by the API. In many cases, they're not extended in any way, and it seems pointless to create a bunch of empty classes.
To avoid this, you might use the JsonResource for the "generic" models and create resources only for those models that include any logic. However, when the time comes to make a customized resource for one of the models, you'll have to update all the places where you previously used the JsonResource.
This is the moment when resource() shines. You simply need to create the customized resource, and the factory will automatically start using it instead of the base resource.
Customization
There are two ways to customize the factory:
- custom map
- custom naming strategy
To change any of them, you'll have to publish the config files:
License
The package is open-sourced software licensed under the MIT license.
