Configs appear to work only when opening DLT through NodeJS implementation

[Ulenspiegel]

I'm not quite certain if it's a known issue (or issue on my side), but it would seem that opening log files through built-in implementation or via adlt results in having no configs on the left pane (just flat list of filters). Opening the same file, in the same session, through deprecated NodeJS implementation does show the configs.

Minimal test setup included just the following in the config file:

    "dlt-logs.configs": [
        {
            "name": "Test",
        }
    ],

No other extension-related configuration; opening same DLT file with two different methods results different views of the side panel:

for regular way of opening dlt file.

for the deprecated NodeJS method.

[mbehr1]

@Ulenspiegel hmm. that might well be the case. I'll take a look!

[mbehr1]

@Ulenspiegel see a first implementation for the adlt backend in PR#246. This is missing the config.autoEnableIf feature yet (are you using that?). Will add that as well next.

[Ulenspiegel]

@mbehr1 , amazing, and thank you; I will give it a test. I'm not using config.autoEnableIf so far (I've discovered the extension just recently, didn't adopt everything yet), so it won't break anything on my side.

[Ulenspiegel]

A couple of days of testing, so far looks like everything works perfectly well. :)