version=published and version=1.0 return different results for user with readPublish permissions about mesh HOT 2 CLOSED

Publishing a draft will automatically raise the draft version to the publish version. It it thus no longer possible to distinguish between 1.0 being the draft or publish version. Mesh currently assumes this version is a draft. The selected permission is currently not chosen by the actual type of container. Instead it is chosen by the query parameter value (version=published -> READ_PUBLISH_PERM) all other values fall back to READ_PERM permission. (NodeCrudHandler:439)

In order to fix this we would need to load the desired version and figure out what versions could be applied.

Desired behaviour:

• Loading a node version using the version parameter should always return the node within the draft scope.

from mesh.

I finally figured out what the issue is. I have described the technial issue in #1104
Fixing the problem would however cause a breaking change. I'll continue to track the issue in #1104

from mesh.