So, I'm working on #7188 and thought "hey, it would be great if we had built-in checks that these required parameters were actually specified". Especially since the current mount type claims that fstype is required, yet does nothing (other than break things after a successful run) if it's not specified (tested using 2.7.x on Solaris).
Unfortunately, it looks like calling isrequired from within the block of newproperty doesn't actually do this (largely because it doesn't look like anything is actually checking required?). Has setting isrequired ever worked, or are isrequired and required? Left-overs from an aborted attempt? Is there an implemented way of doing 'this parameter is required; fail at compile time'? Hopefully without having to do a defaultto of a bogus value, and having a validation failure against that. -- Jacob Helwig
signature.asc
Description: Digital signature
