hostnet/entity-tracker-bundle

Wraps around the hostnet/entity-tracker-component and allows configuration of several listener components

Maintainers

Details

github.com/hostnet/entity-tracker-bundle

Source

Issues

Installs: 97 834

Dependents: 0

Suggesters: 0

Security: 0

Stars: 7

Watchers: 6

Forks: 6

Open Issues: 1

2.0.4 2024-06-03 15:18 UTC

Requires

Requires (Dev)

Suggests

MIT 81338c2e157e22513f81adadca8e830c1bf67808

This package is auto-updated.

Last update: 2024-11-03 16:07:47 UTC

README

Documentation

What is the Entity Tracker Bundle?

The Entity Tracker Bundle is a bundle used to configure the following components:

It will let you configure those components using the config.yaml

Note: Only the Entity Tracker Component is mandatory, as this bundle configures the services. The other components only need to be configured if they are present.

Requirements

The tracker bundle requires at least php 7.3 and runs on Doctrine2 and Symfony2. For specific requirements, please check composer.json

Installation

Installing is pretty easy, this package is available on packagist. You can register the package locked to a major as we follow Semantic Versioning 2.0.0.

Example

    "require" : {
        "hostnet/entity-tracker-bundle" : "^2.0.0"
    }

Note: You can use dev-master if you want the latest changes, but this is not recommended for production code!

Documentation

How does it work?

It features a config builder that allows you to config only what you need. If you have the "Blamable" annotation available, it will throw an exception during container compilation if it's not configured. The same goes for all other supported components. If you happen to configure it while it isn't used, it will also let you know.

Setup

Register The Bundle in your AppKernel

This bundle is not dependent on others based on compiler passes or configuration.

class AppKernel extends Kernel
{
    public function registerBundles()
    {
        $bundles = [
            // ...
            new Hostnet\Bundle\EntityTrackerBundle\HostnetEntityTrackerBundle()
            // ...
        ];

        return $bundles;
    }
}

Configuration Overview

By default, nothing is required. Only when you enable a certain configuration option, it will yell you what's missing.

If you are using entities in your bundle, your bundle should have a dependency on the component using the specific annotation you use. If your bundle is in your application, your application should have a dependency on the component. If you use the hostnet/entity-plugin-lib, you will have separate packages for entities. You should put your dependencies on that package.

Note: Based on what is available, the configuration requirements are determined. If one of the bundles or Entity packages has a dependency on one of the components, this bundle will also configure it for you.

The template is as following:

# Default configuration for extension with alias: "hostnet_entity_tracker"
hostnet_entity_tracker:

    # Configures and enables the blamable listener
    blamable:

        # Provider implementation of Hostnet\Component\EntityBlamable\Provider\BlamableProviderInterface
        provider: ~ # Required

    # Configures and enables the revision listener
    revision:

        # Factory implementation of Hostnet\Component\EntityRevision\Factory\RevisionFactoryInterface
        factory: ~ # Required

    # Configures and enables the mutation listener
    mutation: ~
Configuring the Blamable Component

The Blamable Component has 1 required option, the provider. The provider is the class that implements the BlamableProviderInterface as explained in the documation. The argument passed to that option is the name of the service you are using for it. There are two ways you can go about using these providers. The first way is to make use of the default blamamable provider that is shipped with this bundle. This can be done using the following method:

config.yaml

hostnet_entity_tracker:
    blamable:
        provider: entity_tracker.provider.blamable
        default_username: "username for example purposes"

It is also possible to create your own BlamamableProvider by implementing the BlamableProviderInterface. If you choose to do this the following method can be used to make use of your custom BlamableProvider.

Note: The following example is based on the AcmeBlamableProvider from the link above

services.yaml

services:
    acme.provider.blamable:
        class: Acme\Bundle\AcmeBundle\Service\AcmeBlamableProvider
        arguments:
            - 'username for example purposes'

config.yaml

hostnet_entity_tracker:
    blamable:
        provider: acme.provider.blamable
Configuring the Mutation Component

The Mutation Component has no required options. All you have to do to enable it, is add "mutation: ~" to the config.

config.yaml

hostnet_entity_tracker:
    mutation: ~
Configuring the Revision Component

The Revision Component has 1 required option, the factory. The factory is the class that implements the RevisionFactoryInterface as explained in the documation. The argument passed to that option is the name of the service you are using for it.

Note: The following example is based on the AcmeRevisionFactory from the link above

services.yaml

services:
    acme.factory.revision:
        class: Acme\Bundle\AcmeBundle\Service\AcmeBlamableProvider
        arguments:
            - 'author->name for example purposes'

config.yaml

hostnet_entity_tracker:
    revision:
        factory: acme.factory.revision