genofire
genofire
greate, hope i do not drift away, and maybe write testcases, then i could merge it :) here i found fakeclient: https://github.com/influxdata/influxdb-client-go/blob/master/internal/examples/fakeclient.go
Thank you for your review :)
In which output or database do you like this feature?
sorry for the delay. yes that was my question ... my self i think we should not put that in router or yanic and parse it all the way till...
see https://github.com/FreifunkBremen/yanic/issues/218#issuecomment-1724167659
should we fetch the nodeID here, of the gateway? like in output/meshviewer-ffrgb: https://github.com/FreifunkBremen/yanic/blob/dfd456bc1e8d35bcd6e44cdc653b50d174860160/output/meshviewer-ffrgb/struct.go#L153
you are correct, that it needs a refactory to get nodes ... to manage it, i need to look and test myself ... first tought, do we have something equal...
thats correct, we need therefore a bypass of parameter ... current i am to lazy for developing it, sry. every component on freifunk use this port, so i will focus...
A gateway is also just a node from respondd / yanic view, so there is no easy data struct, to store somethink like this nice. It is possible to save...
Nice but my main problem is that my babel support is not merged over years - so I often have to rebase it. The multidomain support and his unreviewed broken...