With the release of #337 nearing, I'm thinking it may be time to sunset the config component. It started off being the core for defining params/configuration to the framework component, but that was removed in favor of the ADI.configure stuff. Only thing left in it at the moment is the custom annotation feature.
It would make sense to just drop this component and merge the custom annotation feature into another component, probably the DI one. This would be one less component to maintain, and possibly provide an avenue for a tighter integration with the DI component. E.g. something like https://github.com/symfony/symfony/pull/39897.
I don't think there's a way to have callbacks at compile time, so TBD on how it would exactly look, but is worth exploring.
With the release of #337 nearing, I'm thinking it may be time to sunset the config component. It started off being the core for defining params/configuration to the framework component, but that was removed in favor of the
ADI.configurestuff. Only thing left in it at the moment is the custom annotation feature.It would make sense to just drop this component and merge the custom annotation feature into another component, probably the DI one. This would be one less component to maintain, and possibly provide an avenue for a tighter integration with the DI component. E.g. something like https://github.com/symfony/symfony/pull/39897.
I don't think there's a way to have callbacks at compile time, so TBD on how it would exactly look, but is worth exploring.