Attention is currently required from: fixeria, laforge.
2 comments:
File config/sys.config:
Patch Set #8, Line 24: %% {enft_kpi_enable, true}, %% whether to enable the NFT KPI module (default: false)
> IMHO the fact that you are using enftables is totally irrelevant ... […]
"nft" is a well known and established system-wide component, which users can easily understand from general knowledge. Since the code is operating on a system-wide component shared with other stuff running in the system, I consider this to be important enough to be something to tell the user, specially since one of the params is totally directly related to the fact that "nft" is used ("nft_kpi_table_name").
gtpu_kpi would also be definetly better than "enft", because again GTPU is some well known component which means user doesn't need to figure out what "enft" means in this particular context.
If for you proepr naming of configuration parameters which is to be read and set by users is a "trivial detail" and equals the color of a bikeshed, then so be it an I have nothing more to say.
If you think joining the all-is-bikeshed trend is really helping here, also I have nothing more to say.
In any case, I already provided a +1 beforehand, do as you please, my argument have been given.
File rebar.config:
Patch Set #8, Line 13: {git, "https://gitea.osmocom.org/vyanitskiy/enftables.git", {branch, "fixeria/json"}}},
Again, I'll move the library to https://gitea.osmocom.org/erlang/ and push an updated patch revision soon (before merging it)
That's exactly what I meant, sorry if it was not clear, fine with it.
To view, visit change 40281. To unsubscribe, or for help writing mail filters, visit settings.