Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add "has attribute" collectors #42037

Open
xepozz opened this issue Jul 8, 2021 · 1 comment
Open

Add "has attribute" collectors #42037

xepozz opened this issue Jul 8, 2021 · 1 comment

Comments

@xepozz
Copy link
Contributor

@xepozz xepozz commented Jul 8, 2021

Hi everyone.
I need to collect all classes that was registered with some attribute.

For example, I want to have a collection with some classes that was tagged with attribute MyTag. I want to process all these classes with some logic.

I can explain my request in abstract code

#[MyTag]
class TaggedClass1 {}

#[MyTag]
class TaggedClass2 {}

Then I want to collect them and pass to another class:

services:
  _has_attribute:
    MyTag:
      tag: [ 'tagged_with_attribute' ]

  SomeService:
    arguments: [ !tagged_iterator 'tagged_with_attribute' ]

And then I want to process all these classes:

class SomeService 
{
    public function __construct(iterable $classes)
    {
        $processor = new SomeProcessor();

        foreach($classes as $class) {
            $processor->process($class);
        }
    }
}

It will allow to process classes by third-party libraries, whom don't need to have specific methods/properties or another behaviour to work with classes.

If you have similar functional please say me where I can read about it.
If you don't mind I can try to do PR, but most likely I will need help with it.

Thanks!


QA:

  1. You can use interface instead of this feature.
    Yes, I can. But interface won't have any methods, it will exist like just a marker. It's OK for userland code, but not for external libraries code.
  2. You can make your own CompilerPass and share it.
    Yes, but it would be great to supports it by default in framework. Also I think community can find more useful use-cases.
@stof
Copy link
Member

@stof stof commented Jul 9, 2021

Your proposal with something in the config file would have to apply only to services registered in that file, for consistency with other features. This kinda defeats the purpose.
The autoconfiguration feature is the one that can manage cases for the whole project. And as of Symfony 5.3, the autoconfiguration can be based on attributes too.

1. Yes, I can. But interface won't have any methods, it will exist like just a marker. It's OK for userland code, but not for external libraries code.

is a third-party library more likely to accept adding your attribute than your interface ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants