Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Dynamic exporters for smartpireadout
Seperation into different binaries is not my intention.
The idea behind is to define a clear structure and keep readout.go to th erequired minimum.
With your pull request, you add multiple lines of code to readout.go.
This makes it hard to maintain common code if each export functionality is implemented there.
This is why I propose the definition of an interface and the implementation export functions in different files.
This way you can add an exporter with an import and the function call within => additional lines.
We could even separate an exporter into a dedicated repository.

In the next days I can re-write the code to give an example at least for MQTT and maybe some other axisting export functions.


Messages In This Thread
RE: Dynamic exporters for smartpireadout - by TriCX - 06.05.2017, 10:49

Forum Jump:

Users browsing this thread: 1 Guest(s)