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

Share API response added new field share_with_user_type #272

Open
2 of 12 tasks
AlexAndBear opened this issue Apr 25, 2022 · 3 comments
Open
2 of 12 tasks

Share API response added new field share_with_user_type #272

AlexAndBear opened this issue Apr 25, 2022 · 3 comments

Comments

@AlexAndBear
Copy link

WHAT Needs to be Documented?

With the PR owncloud/core#40013 we emit a new field called share_with_user_type
which might either be 0 = user or 1 = guest

WHERE Does This Need To Be Documented (Link)?

https://doc.owncloud.com/server/next/developer_manual/core/apis/ocs-share-api.html#response-attributes-2

WHY Should This Change Be Made?

(Optional) What Type Of Content Change Is This?

  • New Content Addition
  • Old Content Deprecation
  • Existing Content Simplification
  • Bug Fix to Existing Content

(Optional) Which Manual Does This Relate To?

  • Admin Manual
  • Developer Manual
  • User Manual
  • Android
  • iOS
  • Branded Clients
  • Desktop Client
  • Other
@phil-davis
Copy link
Contributor

Note: this new field is only emitted for user shares, not for group shares or other shares (like link shares)

@mmattel
Copy link
Contributor

mmattel commented Apr 26, 2022

@janackermann @phil-davis mind to file a PR on master?
Does this need backporting to 10.9 post merging, or will this be 10.10 only?

@phil-davis
Copy link
Contributor

Does this need backporting to 10.9 post merging, or will this be 10.10 only?

It is a new feature, so whatever release it comes in should be a minor version, e.g. 10.10.0 and not a patch release like 10.9.2

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

No branches or pull requests

3 participants