Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/templates/zerver/api/reorder-custom-profile-fiel...

34 lines
712 B
Markdown
Raw Normal View History

apidocs: Replace hardcoded titles with generated ones. This commit replaces the hardcoded titles of /api pages with the auto-generated ones from the openapi data using the markdown processor.
2021-05-22 13:21:18 +02:00
{generate_api_title(/realm/profile_fields:patch)}
api docs: Document PATCH /realm/profile_fields endpoint.
2020-07-04 13:09:52 +02:00
{generate_api_description(/realm/profile_fields:patch)}
## Usage examples
{start_tabs}
{tab|python}
apidocs: Migrate admin_config out of templates. Currently, the `admin_config` configuration was hardcoded in the templates, but as a goal of creating a common template, we need to move all configurations outside. Moved the checking for function and language which need admin_config out of templates into the code and added a boolean `x-admin-config` to store whehter the operation requires admin config. Also, added the banner for admin access to auto-generate if admin_config is present, and fixed the admin_config for endpoints that were earlier missing it in the templates.
2021-06-11 20:07:45 +02:00
{generate_code_example(python)|/realm/profile_fields:patch|example}
api docs: Document PATCH /realm/profile_fields endpoint.
2020-07-04 13:09:52 +02:00
apidocs: Automatically add javascript example tabs. The javascript tab in .md templates can be generated along with the line that adds js example. Further, as a part of the effort of moving towards a single template, the markdown extension for javascrit examples is modified to return empty string if javascript example doesn't exist for that endpoint. This would make it possible to cover more endpoints with a single template. The js example tabs are now automatically generated during generation of javascript code, and so need to be removed. Also, the markdown function to render js examples can be added in all templates, since it is parses and returns an empty string if the examples don't exist, and allows us to move towards a common template. The pages have been verified to be correct by using diff between old and new pages' raw HTML.
2021-06-02 18:36:25 +02:00
{generate_code_example(javascript)|/realm/profile_fields:patch|example}
api docs: Document PATCH /realm/profile_fields endpoint.
2020-07-04 13:09:52 +02:00
{tab|curl}
{generate_code_example(curl)|/realm/profile_fields:patch|example}
{end_tabs}
## Parameters
{generate_api_arguments_table|zulip.yaml|/realm/profile_fields:patch}
## Response
{generate_return_values_table|zulip.yaml|/realm/profile_fields:patch}
#### Example response
{generate_code_example|/realm/profile_fields:patch|fixture(200)}
apidocs: Fix response in API templates. 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
2021-06-07 22:53:29 +02:00
{generate_code_example|/realm/profile_fields:patch|fixture(400)}