Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/templates/zerver/api/fixtures.json

67 lines
2.2 KiB
JSON
Raw Normal View History

api/render-message: Make code examples and fixtures testable. This commit uses the Markdown extension defined in zerver/lib/bugdown/api_generate_example to generate the example fixture and code example, so that both are tested in tools/lib/api_tests.
2018-01-26 22:11:42 +01:00
{
api: Fix response fixtures for delete_queue. These were malformed.
2018-06-01 21:33:57 +02:00
"bad_event_queue_id_error": {
"code": "BAD_EVENT_QUEUE_ID",
"msg": "Bad event queue id: 1518820930:1",
"queue_id": "1518820930:1",
"result": "error"
},
json: Ensure consistent formatting in api/fixtures.json. Now, the fixtures.json file: * Has all keys sorted alphabetically. * Has a space after every `:`. The file was generated using json.dumps with the appropriate formatting parameters.
2018-03-02 22:04:25 +01:00
"invalid-api-key": {
"msg": "Invalid API key",
"result": "error"
api/get-profile: Make code examples/fixtures testable. This commit uses the Markdown extension defined in zerver/lib/bugdown/api_generate_examples to generate the example fixture and code example, so that both are tested in zerver/lib/api_test_helpers.
2018-01-31 06:06:56 +01:00
},
json: Ensure consistent formatting in api/fixtures.json. Now, the fixtures.json file: * Has all keys sorted alphabetically. * Has a space after every `:`. The file was generated using json.dumps with the appropriate formatting parameters.
2018-03-02 22:04:25 +01:00
"missing-request-argument-error": {
"code": "REQUEST_VARIABLE_MISSING",
"msg": "Missing 'content' argument",
"result": "error",
"var_name": "content"
api docs: Add page for common error payloads. We now have a separate page for common error payloads, for example, the payload for when the client's API key is invalid. All error payloads that are presented on this page will be tested similarly to our other non-error sample fixtures.
2018-02-06 21:04:07 +01:00
},
api: Fix response fixtures for delete_queue. These were malformed.
2018-06-01 21:33:57 +02:00
"successful-response-empty": {
"msg": "",
"result": "success"
},
api docs: Test sample fixture for message edit permission error. In templates/zerver/api/update-message.md, we have a sample fixture for when a zulip.Client does not have the permission to update/edit a particular message. This commit adds a test for that fixture. Also, tools/test-api now also uses a non-admin client for this test, which might come in handy in the future.
2018-02-16 21:26:43 +01:00
"update-message-edit-permission-error": {
json: Ensure consistent formatting in api/fixtures.json. Now, the fixtures.json file: * Has all keys sorted alphabetically. * Has a space after every `:`. The file was generated using json.dumps with the appropriate formatting parameters.
2018-03-02 22:04:25 +01:00
"code": "BAD_REQUEST",
"msg": "You don't have permission to edit this message",
"result": "error"
api_docs: Document the `POST /api/v1/user_uploads` endpoint. Fixes #1353.
2018-02-25 01:01:45 +01:00
},
json: Ensure consistent formatting in api/fixtures.json. Now, the fixtures.json file: * Has all keys sorted alphabetically. * Has a space after every `:`. The file was generated using json.dumps with the appropriate formatting parameters.
2018-03-02 22:04:25 +01:00
"user-not-authorized-error": {
"code": "BAD_REQUEST",
"msg": "User not authorized for this query",
"result": "error"
outgoing-webhooks.md: Add example payloads/fixtures.
2018-06-02 15:45:18 +02:00
},
"zulip-outgoing-webhook-payload": {
"data": "@**Outgoing Webhook Test** Zulip is the world\u2019s most productive group chat!",
"trigger": "mention",
"token": "xvOzfurIutdRRVLzpXrIIHXJvNfaJLJ0",
"message": {
"subject": "Verona2",
"sender_email": "iago@zulip.com",
"timestamp": 1527876931,
"client": "website",
"submessages": [
],
"recipient_id": 20,
"subject_links": [
],
"sender_full_name": "Iago",
outgoing webhooks: Call finalize_payload on payloads. Apparently, the refactor months ago that introduced finalize_payload wasn't applied to the outgoing webhook code path, resulting in message dicts with an unexpected format with no avatar_url and some extra values that were intended to be internal details not relevant to external clients. Because this API is not widely used, we expect there to be little to no impact of converting this back to matching the `get_messages` interface, as it once was and has always been intended to be. The one somewhat tricky detail is that we include both the `content` and `rendered_content` fields, rather than asking the client to pick which they want via the `apply_markdown` flag, because there is no place for the client to configure that setting.
2019-11-05 20:35:47 +01:00
"avatar_url": "https://secure.gravatar.com/avatar/1f4f1575bf002ae562fea8fc4b861b09?d=identicon&version=1",
outgoing-webhooks.md: Add example payloads/fixtures.
2018-06-02 15:45:18 +02:00
"rendered_content": "<p><span class=\"user-mention\" data-user-id=\"25\">@Outgoing Webhook Test</span> Zulip is the world\u2019s most productive group chat!</p>",
"sender_id": 5,
"stream_id": 5,
"content": "@**Outgoing Webhook Test** Zulip is the world\u2019s most productive group chat!",
"display_recipient": "Verona",
"type": "stream",
"id": 112,
"is_me_message": false,
"reactions": [
],
"sender_realm_str": "zulip",
outgoing webhooks: Call finalize_payload on payloads. Apparently, the refactor months ago that introduced finalize_payload wasn't applied to the outgoing webhook code path, resulting in message dicts with an unexpected format with no avatar_url and some extra values that were intended to be internal details not relevant to external clients. Because this API is not widely used, we expect there to be little to no impact of converting this back to matching the `get_messages` interface, as it once was and has always been intended to be. The one somewhat tricky detail is that we include both the `content` and `rendered_content` fields, rather than asking the client to pick which they want via the `apply_markdown` flag, because there is no place for the client to configure that setting.
2019-11-05 20:35:47 +01:00
"sender_short_name": "iago"
outgoing-webhooks.md: Add example payloads/fixtures.
2018-06-02 15:45:18 +02:00
},
"bot_email": "outgoing-bot@localhost"
api/render-message: Make code examples and fixtures testable. This commit uses the Markdown extension defined in zerver/lib/bugdown/api_generate_example to generate the example fixture and code example, so that both are tested in tools/lib/api_tests.
2018-01-26 22:11:42 +01:00
}
}