mi-hol
@turboencabulator would perhaps reviewing this PR work for you? In that case please assign yourself as "reviewer"
@mmehari @turboencabulator Great conversation, resulting in further improvements! This is collaboration at its best! > _Note_: it is possible that the frequency response plot jumps steps without plotting them. The...
> it is more like a limitation of the applied methodology Thanks for clarification
> That's exactly what I was looking for. @turboencabulator  Marking all comments as "resolved" via button  would complete the review "officially" and open the merge window. Example of...
> This is awesome! Great to see these enhancements! @MatthewSteeves would you perhaps mind to become the beta tester?
> First time using the review feature with success! @mmehari LGTM (from list of code-review acronyms at https://www.codelantis.com/blog/code-review-acronyms-lgtm-nit) Please go ahead and merge code, then update wiki
@mck1117 would this PR fit with ongoing cleanups?
@jagedlion is this still an open issue?
great achievement! Another area to add is from my view "production monitoring" to prevent outages as in https://github.com/ixs/tasmota-sml-parser/issues/13
Having consistent coding styles makes perfect sense! Therefore I would suggest `indent_size = 4` for all languages