JSON like DSL instead of CSVs

[john30]

No description provided.

[koen-lee]

I think this is a good idea that will make contributing easier. The CSVs have quite a learning curve and are error-prone.
Could you elaborate on the reasoning of removing it from the milestone?

[john30]

It is still on the road map and actually I was browsing for good JSON libs last week for another thing. Anyway, this is a very time consuming thing to do and it will still take a while. In the meanwhile I'm working on a web UI that is supposed to allow clicking configs together and talk directly to ebusd to update the definitions online.

[anticultist]

Maybe a intermediate json format could be a good starting point. So you can transform between the json format and the current csv based format back and forth but ebusd would only understand the "old" csv based format. With this approach you could test a new json based configuration without rewriting the existing code.

By the way do you know json schema? It is a powerful json-based meta-description of the structure of a json file. With that you can get error checking or auto-completion in modern code editors like VS Code while you work with a json file. Maybe it could be useful here.

[john30]

thats already there and of course I know json schema and there is a schema for what ebusd offers on its http port already in the openapi spec. the same schema is also produced by ebusd when using --dumpconfig=json

nevertheless I'm already working on that topic, recently by using typespec

[john30]

a lot of work has been put into this in the last weeks in ebus-typespec, ebusd-configuration, as well as ebusd itself and ebus-notebook.
the (intermediate) result of all that ends in https://ebus.github.io/ which is the new webservice to be used from the next version of ebusd.