Download the PHP package php-alchemist/doctrine-behaviors without Composer
On this page you can find all versions of the php package php-alchemist/doctrine-behaviors. 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 doctrine-behaviors
DoctrineBehaviorsBundle
A simplified doctrine extension to add common behaviors
Yet another fun-filled doctrine-behaviors-bundle. It isn't designed to be the end-all-be-all of DoctrineBehaviorsBundles, it's just the way we prefer it and the way that we use it. If this works for you great! We're excited you picked ours. If not, no hurt feelings.
Installation
Prior to adding the DoctrineBehaviorsBundle, you will need to add the PHPAlchemist symfony recipes repo to your configuration.
To do so, add the following to your composer.json file:
Next you can require the bundle:
Configuration
In your config/packages folder you should now find a php_alchemist_doctrine_behaviors.yaml file. The contents
should resemble:
If you have a custom decision service in which your Behaviors will look to decide if they should be executed, here is
where you will configure that.
The decision_service option should be filled in with class.
Such as:
This class will replace the default one provided by the bundle.
Turning behaviors off
Every behavior is on by default. If you only want some of them, switch the rest
off under behaviors:
A behavior switched off here is removed from the container entirely — no
service, no Doctrine event listener, and no decide() call on flush. That makes
it cheaper than a decision service that returns false, which still pays the
lookup on every event.
The two options layer, and it is fine to use both:
| Question it answers | When it runs | |
|---|---|---|
behaviors |
Should this listener exist at all? | Compile time |
decision_service |
Should it act on this flush? | Runtime, per event |
| Entity interface | Does this entity opt in? | Runtime, per entity |
So behaviors is the right place for a behavior you never want, and
decision_service is the right place for one you want to toggle at runtime —
from a feature flag, an environment, or a per-tenant setting.
The bundle's own DecisionService honors behaviors too, so the config works
without writing any class. If you supply your own decision_service, that class
owns the decision completely and is not handed the behaviors map — but
anything switched off under behaviors is already gone from the container, so
your class is never asked about it.
