Customization of identifier template

[roxblnfk]

I offer a more flexible option for formatting an identifier for use with a container than in #31

For the case of @mj4444ru the injector setting will be as follows:

(new Injector($container))->withIdTemplate(
    Injector::TEMPLATE_PARAM_CLASS . '$' . Injector::TEMPLATE_PARAM_NAME,
    Injector::TEMPLATE_PARAM_CLASS
);

Todo

• [x] More markers
• [ ] Better naming
• [ ] Documentation
  • [ ] Ru
  • [ ] En
  • [ ] Comments
• [ ] More test

[samdark]

The idea is more sophisticated but naming should be adjusted.

[samdark]

@mj4444ru what do you think?

[mj4444ru]

The idea is interesting and gives more possibilities.

In general, I believe that the container should be able to process such requests in one call, the second (third) call is needed for containers that cannot work with this format (But I'm not sure if this is correct for cascading/complex containers).

I propose to add the following logic to this functionality:

• The container can process identifiers of the format "id$param1$param2$param3" or, alternatively, "id$param1:param2:param3" in one call.
• The container does not know what is in "paramX".
• The container first looks for the identifier "id$param1$param2$param3", then "id$param1$param2", then "id$param1", then "id".
• By default, there will be a variant as in the example. But the end user can replace the second call for example with Injector::TEMPLATE_PARAM_CLASS . '$'. Injector::TEMPLATE_PARAM_NAME . '$'. Injector::TEMPLATE_CLASS, thus adding support for identifiers with the name of the calling class.

[mj4444ru]

InjectorDependence