-
Notifications
You must be signed in to change notification settings - Fork 113
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
Support OCM v1.0 schema #3757
Support OCM v1.0 schema #3757
Conversation
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
423c0a8
to
e47f910
Compare
1696e4a
to
33fce17
Compare
33fce17
to
d5e784b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you also update the init script for creating the webapp table? https://github.com/cs3org/reva/blob/master/pkg/ocm/share/repository/sql/init.sql#L72
* Support OCM v1.0 schema but bail out if the options aren't empty * Fixes following PR comments
* Support OCM v1.0 schema but bail out if the options aren't empty * Fixes following PR comments
Following cs3org/cs3apis#206, we add the fields to ensure backwards compatibility with OCM v1.0.
However, if we receive a request where the
protocol.options
undocumented object is not empty, we bail out for now. Also, we always send out an emptyprotocol.options
, and use the newly defined properties that (will) come with OCM v1.1. This is reflected in the unit tests as well.Supporting interoperability with existing OCM v1.0 implementations (notably Nextcloud 25) may come in the future once the undocumented options are fully reverse engineered.
Also added
viewMode
to the webapp protocol and adapted the SQL layer.