Download the PHP package php-rpc/cruds without Composer
On this page you can find all versions of the php package php-rpc/cruds. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download php-rpc/cruds
More information about php-rpc/cruds
Files in php-rpc/cruds
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 cruds
PHP Cruds bundle
Features
The main purpose of this library it to create easy configurable and extensible API for entities:
- Read controller with flexible entity querying and filtering
- Create and update controllers with easy entity lifecycle control
- Basic access checks
Installation
-
Require package from packagist:
- Include bundle into your application kernel
Doctrine bundle is mandatory to include too as it provides the common "@doctrine" service.
That's all, you are ready to go!
Configuration
See Configuration reference
Usage
See usage manual
Hooking (Event system)
See usage manual
Dependencies
Currently the main dependency is doctrine/common library which provides the
Criteria and the Selectable interface as powerful tool to configure fetch the entities.
Second important dependency is doctrine/doctrine-bundle providing the doctrine registry.
You can implement and override it though.
Integrations
See integration reference
Current limitations
Property mapper
Currently only application-wide API property mapper is supported. This happens because you can use the relations during the criteria configuration and the mapper used for the one entity should handle all of them.
This means that you cannot use both jms/serializer and symfony/serializer as
api metadata provider at the same time, you have to choose and convert mappings.
All versions of cruds with dependencies
doctrine/common Version ^2.4.1
doctrine/doctrine-bundle Version ^1.3
symfony/config Version ~2.7 | ~3.0 | ~4.0
symfony/yaml Version ~2.3 | ~3.0 | ~4.0
symfony/dependency-injection Version ~2.8 | ~3.0 | ~4.0
symfony/http-kernel Version ~2.7 | ~3.0 | ~4.0
symfony/property-access Version ~2.7 | ~3.0 | ~4.0