That’s definitely a strong argument for a strict parser. Maybe adding support for a “comment” property would be a good compromise. The property could be any valued (i.e. string, object, array, whatever).
With such a property allowed it would be possible to write completely valid JSON such that editors and can work with it. From: Francis Dupont <[email protected]><mailto:[email protected]> Date: August 18, 2017 at 8:11:00 AM To: James Sumners <[email protected]><mailto:[email protected]> Cc: [email protected] <[email protected]><mailto:[email protected]>, itay cohen <[email protected]><mailto:[email protected]> Subject: Re: [Kea-users] free text parameter under each subnet James Sumners writes: > Unfortunately the parser doesn't ignore unknown properties. => not unfortunately: it is by design and I am sure you'd like the parser to catch a trivial spelling error than to silently ignore it. Regards Francis Dupont <[email protected]> PS: as you expect to add a new subnet property you need to patch the parser. Note in pools you have the user-context property which can be used for the same goal and can be extended (i.e., post a request) to subnets or other syntax elements (only host reservations will be complex because of external host databases).
_______________________________________________ Kea-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/kea-users
