spec 'erase' param on /account/deactivate #1290
Conversation
| @@ -348,6 +348,11 @@ paths: | |||
| description: |- | |||
| Additional authentication information for the user-interactive authentication API. | |||
| "$ref": "definitions/auth_data.yaml" | |||
| erase: | |||
| description: |- | |||
| Indicates whether the account should be erased. Defaults to `false`. | |||
There was a problem hiding this comment.
What is the server expected to erase?
There was a problem hiding this comment.
I copied the doc comment from js sdk :(
|
Spec proposal? |
|
the issue is marked as |
|
I disagree that this is a spec omission. All of the stuff added for GDPR needs to go through the formal proposal process before it's added to the spec. It's not like this is stuff that's been implemented in riot-web/synapse for forever and we're just documenting it now. This is behavior that's been added either after the proposal process was implemented or close to concurrent with it. |
|
Then the triaging needs to change. |
|
There's been quite a few mentions that I'll add this to the bucket of GDPR things though |
|
ok let's close this for now pending a GDPR spec. |
Fixes https://github.com/matrix-org/matrix-doc/issues/1288