EdColeman commented on PR #3913:
URL: https://github.com/apache/accumulo/pull/3913#issuecomment-1787797012
I was looking into adding a new PropertyType that would be in addition to
the String type and allow testing to see if it was a valid json string. That
would still likely leave a hole for validation that it was "proper" in respect
to its usage and should still be handled when "used". Say `{ "maxThreads",
"10", ... }` was expected by the user and `{ "myValue", "default", ...}` was
passed. If they are both "valid" JSON, that would not make one or the other as
invalid for usage.
If there was a PropertyType.JSON - would that change your approach to this?
It could at least handle checking that the JSON string was valid.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
