Whenever getting arbitrary configuration data serialised to string, e.g. over the network, the confight library doesn’t allow parsing/loading it directly.
It’s only possible to load a file path via the public API, which forces the creation of a named pipe in the above scenario.
Whenever getting arbitrary configuration data serialised to string, e.g. over the network, the
confightlibrary doesn’t allow parsing/loading it directly.It’s only possible to load a file path via the public API, which forces the creation of a named pipe in the above scenario.