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
A few weeks ago the utbot-analytics and all related stuff was removed from the utbot-intellij module.
Now it's time to return it but with a few requirments of @denis-fokin
But usage of utbot - analytics involves some configuration and addition of some fabric implementations from the utbot-analytics during the utbot-intellij initialization before test generation process
Expected behavior
utbot-analytics and all sub-modules that will be extracted from it with the different ML modules should be easily added/removed without any imports from utbot-analytics module in the code
Only comment/uncomment utbot-analytics in the Gradle file should lead to the addition or removal of the ML Path Selector functionality
Solution
We need to implement kind of DI mechanism (slightly reminds Spring work behind the scene)
utbot-intellij load/instantiate the class by its class name from the special config in resources (probably in utbot-analytics module, if possible) or in the utbot-settings
instance of class described in the utbot-analytics or its extracted modules is created and auto-configure or ML Path Selector
The text was updated successfully, but these errors were encountered:
This is a sub-task for the umbrella ticket #703
Description
A few weeks ago the utbot-analytics and all related stuff was removed from the utbot-intellij module.
Now it's time to return it but with a few requirments of @denis-fokin
But usage of utbot - analytics involves some configuration and addition of some fabric implementations from the utbot-analytics during the utbot-intellij initialization before test generation process
Expected behavior
Solution
We need to implement kind of DI mechanism (slightly reminds Spring work behind the scene)
The text was updated successfully, but these errors were encountered: