Check if config is compatible with UI editor

[bramkragten]

Just for the entities editor now.
Extra keys are not allowed:

Some config is not supported by the UI editor:

And missing required elements:

Fixes: #2124

[balloob]

Let's create a helper so we can write code like this:

verify(config, reqKeys, optKeys);

for (const entity of config.entities) {
  verify(entity, reqEntKeys, optEntKeys);
}

[bramkragten]

Yeah was thinking the same

[balloob]

Maybe we should consider https://json-schema.org/learn/miscellaneous-examples.html ?

[balloob]

Should we add a superstruct that validates entity ID and icon to be valid format?

• entity ID: should contain a .
• icon: should contain :

[bramkragten]

yeah we should! 👍

[balloob]

So nice!

[balloob]

I am wondering, this is something we should probably export from the hui-entities-card so it can validate the config there too ?

[balloob]

Ah nevermind, the config editor only supports a subset so needs their own.

[bramkragten]

Probably, but the struct of the editor is a little bit simpler as it doesn't support special rows etc.

[balloob]

yet 😉

[balloob]

I wonder if we can have our special struct register types that validate objects.

So we can have something like

const struct = superstruct({
  'divider-row': validateDividerRow,
  'entity-row': validateEntityRow,
})

const validate = struct({
  entities: ['divider-row|entity-row']
})

[bramkragten]

And use a struct inside validateDividerRow? Or just use a struct instead of superstruct, will make code a little bit more ugly though...

[balloob]

yeah use a struct inside the validator, if that can work. Was just thinking out loud.

[balloob]

Very nice!

[balloob]

This can be merged and the other things can wait for a future PR