Download the PHP package api-skeletons/zf-doctrine-repository without Composer

On this page you can find all versions of the php package api-skeletons/zf-doctrine-repository. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

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 PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • 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.
Please rate this library. Is it a good library?

Example code of api-skeletons/zf-doctrine-repository

Informations about the package zf-doctrine-repository

zf-doctrine-repository

Build Status Gitter Total Downloads

This is a replacement for the default repository structure of Doctrine ORM. This replacement implements a plugin architecture for extensisons to repositories.

For instance, if you need access to an encryption/decryption resource inside your repository you could implement it as a plugin accessible as

Why use this repository structure?

The default repository for Doctrine ORM gives no access to resources outside Doctrine. And the Doctrine ORM Object Manager does not give access to a dependency injection container. So when your applications require more from their repositories the only option is to write your own dependency injection enabled repository factory. To create a standard way to organize this dependency injection repository factory: this is an acceptable solution.

Installation

Installation of this module uses composer. For composer documentation, please refer to getcomposer.org.

Once installed, add ZF\Doctrine\Repository to your list of modules inside config/application.config.php or config/modules.config.php.

zf-component-installer

If you use zf-component-installer, that plugin will install zf-doctrine-repository as a module for you.

Configuration

No manual configuration is required to use this module.

This module makes these changes to your doctrine.entitymanager.orm_default configuration:

If your application already has a default repository class you can edit it to implement ZF\Doctrine\Repository\ObjectRepositoryInterface and the RepositoryFactory can use it.

Creating a Plugin

The config key for the repository plugin service locator is zf-doctrine-repository-plugin. Your plugin must implement ZF\Doctrine\Repository\Plugin\PluginInterface

The __construct of your Plugin will take an array including the repository and any other parameters. Access to the repository gives you access to the ObjectManager.

Use the testing boolean plugin and testing boolean plugin configuration as a template.

Available Plugins

zf-doctrine-repository-query-provider - zfcampus/zf-apigility-doctrine includes Query Providers which may take the current authenticated user and add complex filters to a a QueryBuilder object in order to filter whether the user has access to a given entity. This filtering mechanism can be used across a whole application whenever authorized access is needed to an entity.

Future Plugin Plans

This repository is forward-looking and architected to support the needs today and into the future. Here are examples of repository plugins to be developed:

zf-doctrine-repository-audit - A trigger-happy application will create a structure of triggers on all tables accessible as Doctrine entities. Data would be accessible directly or to access the audit data with a plugin:

All versions of zf-doctrine-repository with dependencies

PHP Build Version
Package Version
Requires php Version ^7.1
doctrine/doctrine-orm-module Version ^1.2 || ^2.1
zendframework/zend-servicemanager Version ^3.0
gianarb/angry Version ^0.1.1
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package api-skeletons/zf-doctrine-repository contains the following files

Loading the files please wait ....