digicomp/flowobjectresolving

Last activity on 10 October 2020
  • 35
composer require digicomp/flowobjectresolving

Helper trait offering an easy and standard way to resolve service classes with nice names

1.0.2

Helper trait offering an easy and standard way to resolve service classes with nice names

Homepage
https://github.com/digital-competence/DigiComp.FlowObjectResolving
Version
1.0.2
Type
neos-package
Release Date
26.10.2020 15:05:15
Source
git
Distribution
zip
Requires
Requires (dev)
None
Suggest
None
Provides
None
Conflicts
None
Replaces
None
MIT
  • #dependency injection
  • #flow
  • #neos
5721b73e1061f7a447994a650f32249a902ce833

DigiComp.FlowObjectResolving

This package is here to help your DI to resolve nice human readable names to class names, to the class names which, should be used.

Additionally, it allows you to get a list of all those nice names, so you could list them from a CommandController, if you want to.

class DefaultResolver
{
    use ResolverTrait;

    protected static function getManagedInterface(): string
    {
        return RequestPatternInterface::class;
    }

    protected static function getManagedNamespace(): string
    {
        return 'Security\\RequestPattern\\';
    }
}

This class would for example list the following with a simple getAvailableNames:

['Neos.Flow:ControllerObjectName', 'Neos.Flow:CsrfProtection', 'Neos.Flow:Host',
 'Neos.Flow:Ip', 'Neos.Flow:Uri']

And those plugins can now be resolved to instances with PluginResolver::create('EmptyDir') for example. getDefaultNamespace and getDefaultPackage are optional for your resolver and will be resolved to the class, which used the trait, if not overridden.

The ObjectManagerInterface in getDefaultPackageKey is there, because this function makes use of the CompileStatic feature of flow.

The name is build in the scheme: {packageKey}{namespace}{name} - if you need to have different namespaces for different packages, you should implement your conditions, or even use configuration in getManagedNamespace - you'll get the packageKey as argument (even if not shown above).

Classes which do not follow the default pattern can still be used, and will be listed, with the FQCN.

The content of the readme is provided by Github
The same vendor provides 5 package(s).