decisions: also be strict about specifications

ElektraInitiative · Nov 23, 2020 · 4e894a3 · 4e894a3
1 parent f5eef7b
commit 4e894a3
Showing 1 changed file with 1 addition and 0 deletions.
diff --git a/doc/decisions/error_semantics.md b/doc/decisions/error_semantics.md
@@ -23,6 +23,7 @@ unclear when plugins actually should emit errors and warnings.
 Provide guidelines in the form as tutorials, covering:
 
 - that any not understood metadata (e.g. types), should lead to an error
+- that wrong specifications, like `kdb meta-set /tests/ipaddr/ipv4 check/ipaddr ipv8` should be rejected
 - if the value does not confirm **exactly** to the specified type, an error should be emitted
   (e.g. only `0` or `1` as boolean)
 - anything else that is beyond the capabilities of a plugin, should lead to an error, e.g.: