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
Describe the bug
If I want to create a controller with a underscore in the file name this is not working fully properly. It is loaded by the configuration for that controller is not loaded.
To Reproduce
Steps to reproduce the behavior:
create a customer collector p3exporter/collector/my_example.py
create class MyExampleCollector in my_example
activate collector in p3.yml
put some configuration in collector_opts for your collector
collector_opts will not be loaded correctly
Expected behavior
All configuration defined under collector_opts.my_example should be accessable in self.opts
Versions:
python
3.9.4
Additional context
I think that collector_name_from_class within CollectorBase needs to be adapted to solve that issue.
The text was updated successfully, but these errors were encountered:
With this fix camelized collector names like `FooBarBazCollector` will
lead to module name `foo_bar_baz`.
Adapt docstring to reflect the new behavior. This change is a
non-breaking one.
Describe the bug
If I want to create a controller with a underscore in the file name this is not working fully properly. It is loaded by the configuration for that controller is not loaded.
To Reproduce
Steps to reproduce the behavior:
p3exporter/collector/my_example.py
MyExampleCollector
inmy_example
p3.yml
collector_opts
for your collectorExpected behavior
All configuration defined under
collector_opts.my_example
should be accessable inself.opts
Versions:
3.9.4
Additional context
I think that
collector_name_from_class
withinCollectorBase
needs to be adapted to solve that issue.The text was updated successfully, but these errors were encountered: