Idea
Let's enhance the spo list set command with some additional options.
| Option |
Description |
--versionExpireAfterDays [versionExpireAfterDays] |
Number that defines how many days a version should be removed after. When using this option, be sure to also set majorVersionLimit. |
--versionAutoExpireTrim [versionAutoExpireTrim] |
Boolean that indicates whether the automatic version trim should be enabled. Valid values are: true, false. |
Requests
AFAIK, we'll have to use a CSOM request to set these values.
When implementing this enhancement, make sure that:
versionExpireAfterDays is a valid positive integer (we have a validation function for this).- It is not possible to specify
versionExpireAfterDays and versionAutoExpireTrim (unless the latter is false).
- Currently you'll have to set
enableVersioning to true to make majorVersionLimit work. I don't see a point for this, for me it is obvious when majorVersionLimit is specified that versioning should be enabled. Let's remove this necessity.
Idea
Let's enhance the spo list set command with some additional options.
--versionExpireAfterDays [versionExpireAfterDays]majorVersionLimit.--versionAutoExpireTrim [versionAutoExpireTrim]true,false.Requests
AFAIK, we'll have to use a CSOM request to set these values.
When implementing this enhancement, make sure that:
versionExpireAfterDaysis a valid positive integer (we have a validation function for this).versionExpireAfterDaysandversionAutoExpireTrim(unless the latter isfalse).enableVersioningtotrueto makemajorVersionLimitwork. I don't see a point for this, for me it is obvious whenmajorVersionLimitis specified that versioning should be enabled. Let's remove this necessity.