1fa82c2fcd
Now, the descriptions and all subschemas are directly returned just by `generate_code_example`, and so, these individual subschemas and descriptions can be removed from the templates. All API endpoints docs are exactly the same after the change, except few where missing 400 responses got added due to the modification
981 B
{generate_api_title(/settings/notifications:patch)}
{generate_api_description(/settings/notifications:patch)}
Usage examples
{start_tabs} {tab|python}
{generate_code_example(python)|/settings/notifications:patch|example}
{tab|curl}
{generate_code_example(curl, include=["enable_offline_push_notifications", "enable_online_push_notifications"])|/settings/notifications:patch|example}
{end_tabs}
Parameters
{generate_api_arguments_table|zulip.yaml|/settings/notifications:patch}
Response
Return values
The server will return the settings that have been changed after the request, with their new value. Please note that this doesn't necessarily mean that it will return all the settings passed as parameters in the request, but only those ones that were different than the already existing setting.
Example response
{generate_code_example|/settings/notifications:patch|fixture(200)}
{generate_code_example|/settings/notifications:patch|fixture(400)}