discourse/spec/requests/api/schemas/json/user_create_request.json

{
  "additionalProperties": false,
  "properties": {
    "name": {
      "type": "string"
    },
    "email": {
      "type": "string"
    },
    "password": {
      "type": "string"
    },
    "username": {
      "type": "string"
    },
    "active": {
      "type": "boolean",
      "description": "This param requires an api key in the request header or it will be ignored"
    },
    "approved": {
      "type": "boolean"
    },
    "user_fields[1]": {
      "type": "boolean"
    },
    "external_ids": {
      "type": "object"
    }
  },
  "required": [
    "name",
    "email",
    "password",
    "username"
  ]
}
DEV: Refactor the api docs for the user endpoint (#14377) Due to the way that rswag expands shared components we were getting this warning when linting our api docs: ``` Component: "user_response" is never used. ``` This change refactors the `api/users_spec.rb` file so that it uses the new way of doing things with a separate `user_get_response.json` schema file rather then the old way of loading a shared response inside of the swagger_helper.rb file. 2021-09-20 10:04:57 -06:00			`{`
			`"additionalProperties": false,`
			`"properties": {`
			`"name": {`
			`"type": "string"`
			`},`
			`"email": {`
			`"type": "string"`
			`},`
			`"password": {`
			`"type": "string"`
			`},`
			`"username": {`
			`"type": "string"`
			`},`
			`"active": {`
DEV: Add description for active param on create user api docs (#18753) The `active` param on the create user endpoint requires that an api key is used in the request header otherwise it is ignored, so adding this distinction to the api docs. 2022-10-25 18:24:54 -06:00			`"type": "boolean",`
			`"description": "This param requires an api key in the request header or it will be ignored"`
DEV: Refactor the api docs for the user endpoint (#14377) Due to the way that rswag expands shared components we were getting this warning when linting our api docs: ``` Component: "user_response" is never used. ``` This change refactors the `api/users_spec.rb` file so that it uses the new way of doing things with a separate `user_get_response.json` schema file rather then the old way of loading a shared response inside of the swagger_helper.rb file. 2021-09-20 10:04:57 -06:00			`},`
			`"approved": {`
			`"type": "boolean"`
			`},`
			`"user_fields[1]": {`
			`"type": "boolean"`
FEATURE: API to create user's associated account (#15737) Discourse users and associated accounts are created or updated when a user logins or connects the account using their account preferences. This new API can be used to create associated accounts and users too, if necessary. 2022-03-03 18:17:02 +02:00			`},`
			`"external_ids": {`
			`"type": "object"`
DEV: Refactor the api docs for the user endpoint (#14377) Due to the way that rswag expands shared components we were getting this warning when linting our api docs: ``` Component: "user_response" is never used. ``` This change refactors the `api/users_spec.rb` file so that it uses the new way of doing things with a separate `user_get_response.json` schema file rather then the old way of loading a shared response inside of the swagger_helper.rb file. 2021-09-20 10:04:57 -06:00			`}`
			`},`
			`"required": [`
			`"name",`
			`"email",`
			`"password",`
			`"username"`
			`]`
			`}`