-
Notifications
You must be signed in to change notification settings - Fork 325
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
Client-supported features end-point #1503
Conversation
726291a
to
4e04d1e
Compare
4e04d1e
to
1fe3ea4
Compare
1fe3ea4
to
50d08e3
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.
See inline comments for things to improve; the functionality of storing client input is implemented alright.
However as I don't really see what the plan is to use this information afterwards, this is only a tentative approval of this particular storing functionality, not of a first part of a general plan. i.e. this code may get reverted entirely in the future if the plan how to make use of these features doesn't materialize.
For upcoming PRs please get reviews on the implementation ideas first before writing a lot of code.
13f8632
to
b946968
Compare
This reverts commit e9376d8
(This is useful because in the next commit, we'll have to chop the module skope in half at these types with `makePrism`, and that would break things.)
bd83d9f
to
8a85a04
Compare
b422a3d
to
c4e40b8
Compare
91678b8
to
3cd136c
Compare
https://wearezeta.atlassian.net/browse/SQSERVICES-417
changelog update (and possibly a few lines of documentation) coming up.
TODO:
legalhold
keyword tolegalhold-implicit-consent
feature
tocapability