You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Autoconfigure currently has compileOnly dependencies the exporter modules, along with a bunch of exporter-specific configuration to extract the relevant properties ConfigProperties and configure exporters. It makes autoconfigure pretty cumbersome to maintain, since there are test suites verifying the configured behavior of different exporters.
It would be better for maintainability and separation of concerns if the tests and the configuration code where decentralized and lived in the exporter modules. The stability of :sdk:autoconfigure-spi makes this straight forward to implement.
The text was updated successfully, but these errors were encountered:
Discussed in this comment.
Autoconfigure currently has
compileOnly
dependencies the exporter modules, along with a bunch of exporter-specific configuration to extract the relevant propertiesConfigProperties
and configure exporters. It makes autoconfigure pretty cumbersome to maintain, since there are test suites verifying the configured behavior of different exporters.It would be better for maintainability and separation of concerns if the tests and the configuration code where decentralized and lived in the exporter modules. The stability of
:sdk:autoconfigure-spi
makes this straight forward to implement.The text was updated successfully, but these errors were encountered: