[tests-only] update getPersonalSpaceIdForUser to use new oc:id format #39793
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR makes the code more flexible in
getPersonalSpaceIdForUser
. It auto-detects if the space id is in base64-encoded format (the current "old" format) or in the proposed new unencoded format. So the tests will run auto-magically againstcs3org/reva
with either the old or proposed new format without needing to do anything special in CI.This provides a way to transition to the proposed new format without breaking any CI.
Related Issue
reva PR cs3org/reva#2542
How Has This Been Tested?
CI
cs3org/reva#2550 - CI passes in reva master branch using the code here in this PR.
cs3org/reva#2551 - CI passes in reva edge branch using the code here in this PR.
cs3org/reva#2552 - CI passes in reva edge with the proposed "remove base64 encoding of ids" code from cs3org/reva#2542
Types of changes
Checklist: