Deprecate extended JSON in favor for compliant JSON comments
name: Deprecate extended JSON in favor for compliant JSON comments/includes
Kea DHCP uses an extended JSON format with comments and includes that deviates from "standard" JSON (RFC 8259).
While it is nice to have comments and includes in the configuration file, the current implementation is not compliant with the JSON specs and breaks other tools JSON parser.
For non-trivial Kea DHCP configuration files, it is highly recommended to use a text editor with JSON support (VS Code, VIM, Emacs, BBEdit etc) or a JSON editor. However, the current "extensions" break the JSON support in these tools/editors so that they cannot be used. The loss of these tools is hurting more than the extra functions implemented in the extended JSON format.
I propose that the current extension are being deprecated and replaced with comments and includes that are valid according to the JSON RFC, so that non-Kea tools can be used when working with Kea configuration files.