Unable to use custom `EventSubscriberInterface` in depfile since 2.0 as those are prefixed in the phar about deptrac

[janedbal]

I understand. I just think that Deptrac was very nicely customizable and extendable thanks to its event-driven design and the fact you have access to its DIC. That allowed us some neat customizations we needed. And now it got a bit worse :)

[janedbal]

Yeah, I know the risk and I'm willing to take it. Obviously I'm doing non-standard thing, I just wanna let you know that there are deptrac users that utilize its internal stuff.

[gennadigennadigennadi]

By the way, with the new release model, I can release new version quicker! And I will try do release Deptrac more often!

My next goal is to figure out how we deploy the documentation 😅.

[gennadigennadigennadi]

I’ve merged ‘Deptrac_Internal’ as the namespace prefix for Deptrac a dependencies.

See https://github.com/qossmic/deptrac-src/pull/48/files.
There is not a release wirh the static prefix, so there is still the possibility to change it.

[gennadigennadigennadi]

I don’t think that the internal dependencies have ever been a public api. Properly a better solution would be to have a official extension point which is provided by Deptrac itself.

another option could be to prefix the dependencies with a static prefix. And people could still use those.

[gennadigennadigennadi]

With using the Symfony event from Deptrac your project adds a dependency. And if Deptracs decides to drop the Symfony stuff your code will break.

long story short: Deptrac should define extension points and document them. Maybe that’s already the case @patrickkusebauch ?

[patrickkusebauch]

I think a nice middle ground would be to have a static prefix for the Symfony Event Dispatcher, something like Deptrac\Symfony\Component\EventDispatcher\EventSubscriberInterface. That way the users can depend on a consistent name to extend that would not break between releases.

@janedbal do you think that would be good enough for your use case?

[janedbal]

If you insist on prefixing, then static one is definitelly better. Thank you