Propose version to be a required property for a reviewed preprint

[giorgiosironi]

We have been working on homepage listings which displays some teasers of reviewed preprints.

We have noticed that the schema allows for a reviewed-preprint to not have a version, however we have not found examples in the production data by browsing the website and a couple of pages of the API.

We were wondering if this could be made mandatory, unless there are cases where a reviewed-preprint is allowed not to have a version. The behavior of journal if this case happens is benign (does not explode) but otherwise undefined.

Prerequites

• include version in all samples in api-dummy
• include version in all samples in journal
• make version mandatory in api-sdk-php
• update samples in this PR

[nlisgo]

Creating it as optional allowed the schema to be rolloed out without it already being implemented. I support a change to make it required.

You will have to amend the samples which is probably why tests are failing.

You would need to ensure that all examples in api-dummy include in order to bump the version. Then on to the adjustment in sdk and then journal any mocks will have to include the version in the mock response.

Happy with this change. If you don't bump the version there is no need for EPP to work on the api we supply.