Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add a spaceid to the propfind response #2657

Merged
merged 1 commit into from
Mar 21, 2022
Merged

Conversation

C0rby
Copy link
Contributor

@C0rby C0rby commented Mar 21, 2022

Added the spaceid to propfind responses so that clients have the necessary data to send subsequent requests.
See: owncloud/ocis#3345

@C0rby C0rby requested review from butonic, micbar and kobergj March 21, 2022 16:39
@C0rby C0rby requested review from a team, labkode, ishank011 and glpatcern as code owners March 21, 2022 16:39

// when allprops has been requested
if pf.Allprop != nil {
// return all known properties
response.Propstat = append(response.Propstat, propfind.PropstatXML{
propstatOK := propfind.PropstatXML{
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Copy link
Member

@micbar micbar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@C0rby C0rby merged commit bca5582 into cs3org:edge Mar 21, 2022
@C0rby C0rby deleted the spaceid-trash-bin branch March 21, 2022 17:18
@kulmann
Copy link
Member

kulmann commented Mar 21, 2022

What's the reasoning for naming the property spaceid instead of storageid though? 🤔

@C0rby
Copy link
Contributor Author

C0rby commented Mar 22, 2022

🤷‍♂️ I implemented what was discussed in the linked issue. The storages in the backend are also called spaces so spaceid is technically correct. Storageid would be more generic though. I don't have a preference for either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants