don't clean up the test environment if a data provider was finished
group shares and combine permissions
unit tests for grouping of shares pointing to the same source
generateTarget() will always find a unique target
fix add user to group to work with grouped shares
mark exclude list as deprecated. It neither used by the files app nor by the
calendar or contacts app. It doesn't make sense to build a exclude list by the
share API, the apps knows best which are valid targets.
fix unit tests
only add a new row if it isn't a unique share, otherwise update the existing row
clear share table after each test run
some small fixes
always select permissions, used in getItems()
call \OCP\Share::getItemsSharedWithUser() to get exclude list, this way all checks are executed, e.g. to check if the share is really visible
for group shares only the parent has the up-to-date permission. Make sure that we always use this permission, except if the user permission is '0' because in this case the user unshared the group share from self
for group shares we don't need a extra db entry of groupTarget equals itemTarget
only create a new share entry, if the user needs a different target name than the group share
on unshare only unshare childrens if there is no other parent available
throw a exception if we can't handle the provided path
some small fixed, suggested by scrutinizer