Hard-coded responses in shareInfoToResourceInfo

[michielbdejong]

We still have hard-coded responses from this function
In the case of addReceivedShare it's even a hard-coded JSON string

[ishifoev]

I think we need 2 step work. The first one is that do we need an endpoint from Reva. We just mockup it and have hardcoded data, but we can't take it from the Reva side. But the second one does we need to save in an additional table this permission.

[ishifoev]

On next cloud we have a permission like an integer. But from Reva side we need to save it like array of permissions

"permission_set" => [
				"add_grant" => false,
				"create_container" => false,
				"delete" => false,
				"get_path" => false,
				"get_quota" => false,
				"initiate_file_download" => false,
				"initiate_file_upload" => false,
];

[michielbdejong]

@Triantafullenia-Doumani will look at this this afternoon from 13:00

[michielbdejong]

The values are these: https://github.com/pondersource/nc-sciencemesh/blob/099b11e/lib/Controller/RevaController.php#L251-L306
They should stay in the same response format, but come of the database

[michielbdejong]

Maybe shareInfoToResourceInfo is sometimes used in the role of nextcloudShareObjectToRevaShareTable

[michielbdejong]

Note: the 'permissions' column should be removed from the ScienceMeshShares table. Instead, we store them using getPermissionsCode