From 169cc98101b33bf6062119a932623993a1661700 Mon Sep 17 00:00:00 2001 From: David Baker Date: Fri, 15 Jan 2016 10:04:29 +0000 Subject: [PATCH] M_INVALID_USERNAME to be consistent with the name of the parameter --- api/client-server/registration.yaml | 2 +- specification/client_server_api.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/api/client-server/registration.yaml b/api/client-server/registration.yaml index 5008b477..3818fc34 100644 --- a/api/client-server/registration.yaml +++ b/api/client-server/registration.yaml @@ -100,7 +100,7 @@ paths: Part of the request was invalid. This may include one of the following error codes: * ``M_USER_IN_USE`` : The desired user ID is already taken. - * ``M_INVALID_USER_NAME`` : The desired user ID is not a valid user name. + * ``M_INVALID_USERNAME`` : The desired user ID is not a valid user name. * ``M_EXCLUSIVE`` : The desired user ID is in the exclusive namespace claimed by an application service. diff --git a/specification/client_server_api.rst b/specification/client_server_api.rst index 25fb0b9e..1cd2a49d 100644 --- a/specification/client_server_api.rst +++ b/specification/client_server_api.rst @@ -86,7 +86,7 @@ Some requests have unique error codes: :``M_USER_IN_USE``: Encountered when trying to register a user ID which has been taken. -:``M_INVALID_USER_NAME``: +:``M_INVALID_USERNAME``: Encountered when trying to register a user ID which is not valid. :``M_ROOM_IN_USE``: