Download the PHP package digicomp/flowobjectresolving without Composer

On this page you can find all versions of the php package digicomp/flowobjectresolving. 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 digicomp/flowobjectresolving

Informations about the package flowobjectresolving

DigiComp.FlowObjectResolving

Build status

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.

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

And those plugins can now be resolved to instances with (new DefaultResolver)->resolveObjectName('Neos.Flow:ControllerObjectName') 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.

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

All versions of flowobjectresolving with dependencies

PHP Build Version
Package Version
Requires neos/flow Version ^5.3 | ^6.0 | ^7.0 | ^8.0
php Version ^7.2 | ^8.0
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 digicomp/flowobjectresolving contains the following files

Loading the files please wait ....