any_channel_json_schemas 0.0.1 → 0.0.2

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 0821263b11ec6aaa6bc724dbd42bf8feb0fb6813
4
- data.tar.gz: 671a0af6de074af4d13c14afceca9fcb75d43309
3
+ metadata.gz: c3468bbe39096b7b8963a682864c4c88a1f70147
4
+ data.tar.gz: fb483e80f5eadae3b7ac11276cda390e8e6c5ff0
5
5
  SHA512:
6
- metadata.gz: 055eae9eb4a7027cd8d2674e8efb5e3db980bb88328763815d7d11de7aa59ad3c95b283341cbc0cc8f00c0c94a4d0b6378e28cf9b28bf923cb5c26ce8835a734
7
- data.tar.gz: a8fdb6378cc4ab5854c9a2790fabf9efab5c24c1f50bdc4d6cc0a19f3678b03b273dabf8ee1b3f183ced41fc46602062b69ea67dcd76315d78ebe5e45eeb56a2
6
+ metadata.gz: 46a87735a661497314e6b36c6751cb5c226f7603144a1d3d92d871b4e6c1aed94f0862ec27dbcbe85fe7d6c738d636ea852eb3eb68c2c5daca0e606a0c3b1e1d
7
+ data.tar.gz: 71b4b99da16f0816c02699928fbdc79d8be296978b307fd51bb6dacee035b29c103eb8f8bb46a23f5497005e9e3acdde11b0fab155fe500f3effb4aaea17332c
data/README.md CHANGED
@@ -13,14 +13,19 @@ gem install any_channel_json_schemas
13
13
  The gem exposes a single module with the following methods:
14
14
 
15
15
  ```ruby
16
- manifest
17
- pull_payload
18
- channelback_payload
19
- push_parameters
20
- event_base
21
- event_pull_request
22
- event_create_ris
23
- event_resources_created_from_external_ids
16
+ manifest
17
+ pull_payload
18
+ external_resource
19
+ push_parameters
20
+ channelback_payload
21
+ event_callback_any
22
+ event_callback_base
23
+ event_callback_create_integration
24
+ event_callback_create_integration_instance
25
+ event_callback_destroy_integration
26
+ event_callback_destroy_integration_instance
27
+ event_callback_pull_request
28
+ event_callback_resources_created_from_external_ids
24
29
  ```
25
30
 
26
31
  Each of these returns an absolute path to a schema file. We use these in our own code base with the [json-schema](https://github.com/ruby-json-schema/json-schema) gem both in our test suite and to validate json payloads real-time.
@@ -33,7 +38,7 @@ Here's an example of how use the schemas to validate a [manifest](https://develo
33
38
  if validation_errors.empty?
34
39
  # Manifest conforms to the published schema.
35
40
  else
36
- # There are validation erros and we can't proceed.
41
+ # There are validation errors and we can't proceed.
37
42
  end
38
43
  ```
39
44
 
@@ -3,11 +3,24 @@
3
3
  "properties": {
4
4
  "data": {
5
5
  "type": "object",
6
- "required": ["integration_instance_name", "url", "request_id"],
6
+ "required": ["integration_instance_name", "url", "request_id", "duplicate_external_ids"],
7
7
  "properties": {
8
8
  "integration_instance_name": {"type": "string"},
9
9
  "url": {"type": "string", "format": "https-url"},
10
- "request_id": {"type": "string"}
10
+ "request_id": {"type": "string"},
11
+ "duplicate_external_ids": {
12
+ "type": "array",
13
+ "items": {
14
+ "type": "object",
15
+ "required": ["external_id", "request_id", "ticket_nice_id", "comment_id"],
16
+ "properties": {
17
+ "external_id": {"type": "string"},
18
+ "request_id": {"type": "string"},
19
+ "ticket_nice_id": {"type": "string"},
20
+ "comment_id": {"type": "string"}
21
+ }
22
+ }
23
+ }
11
24
  }
12
25
  }
13
26
  }
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: any_channel_json_schemas
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.0.1
4
+ version: 0.0.2
5
5
  platform: ruby
6
6
  authors:
7
7
  - JaredShay
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2016-11-21 00:00:00.000000000 Z
11
+ date: 2016-11-22 00:00:00.000000000 Z
12
12
  dependencies: []
13
13
  description: JSON schema files for the Zendesk Channels Framework.
14
14
  email: