-
Type: Bug
-
Status: Resolved
-
Priority: Major
-
Resolution: Applied
-
Affects Version/s: None
-
Fix Version/s: V1.0 Errata
-
Component/s: Domain Model
-
Labels:None
-
Proposal:
-
Resolution:
The versioningState parameter is optional and defaults to "major". However, for non-versionable object types, it is required to be "none", which makes versioningState a required parameter in this case. This makes no sense. Proposal - make the default major for versionable documents, none for non-versionable. Or make the parameter not allowed at all for non-versionable.
Note also that 2.9.6 says that repos which do not support versioning "MAY create new Document objects in a Major Version state". If this is so, why is the versioningState param not allowed to be "major"?