Closed elliotcmorris closed 4 days ago
The example potential solution given is not possible since we switched to std::optional
rather than exceptions.
A more breaking change would be to remove the std::optional
ness of required
properties, and throw an exception saying the value should have been set.
Carefully consider this in the context of established rules in our GUIDELINES
I'm going to close this, since it reverses current guidelines, and the proposed solution wouldn't work anyway.
If we add a tag to the yaml schema
required
to each property, there is some validation we can do to be friendlier. Most directly, we can emit a better error message when the property is not set, so the recipient knows the error is not their fault, and knows who to go to to address it.