From 9a9047532f33748b8cf935237120e8f85f7710af Mon Sep 17 00:00:00 2001 From: Andrew Morgan Date: Wed, 19 Jun 2019 13:52:01 +0100 Subject: [PATCH] Change accidental edit --- clientapi/routing/register.go | 19 ++++++++----------- 1 file changed, 8 insertions(+), 11 deletions(-) diff --git a/clientapi/routing/register.go b/clientapi/routing/register.go index 50f352470..b1522e82b 100644 --- a/clientapi/routing/register.go +++ b/clientapi/routing/register.go @@ -108,24 +108,21 @@ var ( // remembered. If ANY parameters are supplied, the server should REPLACE all knowledge of // previous parameters with the ones supplied. This mean you cannot "build up" request params. type registerRequest struct { - // user-interactive auth params - Auth authDict `json:"auth"` - // registration parameters Password string `json:"password"` Username string `json:"username"` + Admin bool `json:"admin"` + // user-interactive auth params + Auth authDict `json:"auth"` + + InitialDisplayName *string `json:"initial_device_display_name"` + + // Prevent this user from logging in + InhibitLogin common.WeakBoolean `json:"inhibit_login"` // Application Services place Type in the root of their registration // request, whereas clients place it in the authDict struct. Type authtypes.LoginType `json:"type"` - - InitialDisplayName *string `json:"initial_device_display_name"` - - // more reg params - Admin bool `json:"admin"` - - // Prevent this user from logging in - InhibitLogin common.WeakBoolean `json:"inhibit_login"` } type authDict struct {