salesforce_streamer 1.1.1 → 1.1.3
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/.travis.yml +3 -2
- data/Gemfile.lock +9 -9
- data/README.md +2 -7
- data/lib/salesforce_streamer/version.rb +1 -1
- metadata +3 -4
- data/CODE_OF_CONDUCT.md +0 -74
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: e012e8556497f5507f2623d8894c61461185bd3204188ed5ad0a7aaf452a74de
|
4
|
+
data.tar.gz: 1049dc30fa1244441e763cbd90229fe8788b269ea4b387a3fad22f256cbaea68
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: ae36d194ebebaa1bd0b85009d84b6689ab1047e8c019617fd1d61dc50d412f6a46e06724948836ec7943516596e39c4cee0a3f0906e9cc53c21dc8010677f47d
|
7
|
+
data.tar.gz: 456bb39dc8fc06b879b6611e6b2abab2b396f988b9daa0e7d191a38823698850267a653909b1471e0c99cdf01a43f00fc49d610cb1978107a8ff5433875cc120
|
data/.travis.yml
CHANGED
data/Gemfile.lock
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
PATH
|
2
2
|
remote: .
|
3
3
|
specs:
|
4
|
-
salesforce_streamer (1.1.
|
4
|
+
salesforce_streamer (1.1.3)
|
5
5
|
faye (= 0.8.9)
|
6
6
|
restforce (~> 4.2)
|
7
7
|
|
@@ -28,10 +28,10 @@ GEM
|
|
28
28
|
em-socksify (0.3.2)
|
29
29
|
eventmachine (>= 1.0.0.beta.4)
|
30
30
|
eventmachine (1.2.7)
|
31
|
-
faraday (0.
|
31
|
+
faraday (1.0.0)
|
32
32
|
multipart-post (>= 1.2, < 3)
|
33
|
-
faraday_middleware (0.
|
34
|
-
faraday (
|
33
|
+
faraday_middleware (1.0.0)
|
34
|
+
faraday (~> 1.0)
|
35
35
|
faye (0.8.9)
|
36
36
|
cookiejar (>= 0.3.0)
|
37
37
|
em-http-request (>= 0.3.0)
|
@@ -49,7 +49,7 @@ GEM
|
|
49
49
|
jwt (2.2.1)
|
50
50
|
multipart-post (2.1.1)
|
51
51
|
parallel (1.19.1)
|
52
|
-
parser (2.7.0.
|
52
|
+
parser (2.7.0.5)
|
53
53
|
ast (~> 2.4.0)
|
54
54
|
public_suffix (4.0.3)
|
55
55
|
rack (2.2.2)
|
@@ -68,21 +68,21 @@ GEM
|
|
68
68
|
rspec-mocks (~> 3.9.0)
|
69
69
|
rspec-core (3.9.1)
|
70
70
|
rspec-support (~> 3.9.1)
|
71
|
-
rspec-expectations (3.9.
|
71
|
+
rspec-expectations (3.9.1)
|
72
72
|
diff-lcs (>= 1.2.0, < 2.0)
|
73
73
|
rspec-support (~> 3.9.0)
|
74
74
|
rspec-mocks (3.9.1)
|
75
75
|
diff-lcs (>= 1.2.0, < 2.0)
|
76
76
|
rspec-support (~> 3.9.0)
|
77
77
|
rspec-support (3.9.2)
|
78
|
-
rubocop (0.
|
78
|
+
rubocop (0.81.0)
|
79
79
|
jaro_winkler (~> 1.5.1)
|
80
80
|
parallel (~> 1.10)
|
81
81
|
parser (>= 2.7.0.1)
|
82
82
|
rainbow (>= 2.2.2, < 4.0)
|
83
83
|
rexml
|
84
84
|
ruby-progressbar (~> 1.7)
|
85
|
-
unicode-display_width (>= 1.4.0, <
|
85
|
+
unicode-display_width (>= 1.4.0, < 2.0)
|
86
86
|
rubocop-performance (1.5.2)
|
87
87
|
rubocop (>= 0.71.0)
|
88
88
|
rubocop-rspec (1.38.1)
|
@@ -92,7 +92,7 @@ GEM
|
|
92
92
|
docile (~> 1.1)
|
93
93
|
simplecov-html (~> 0.11)
|
94
94
|
simplecov-html (0.12.2)
|
95
|
-
unicode-display_width (1.
|
95
|
+
unicode-display_width (1.7.0)
|
96
96
|
url (0.3.2)
|
97
97
|
websocket-driver (0.7.1)
|
98
98
|
websocket-extensions (>= 0.1.0)
|
data/README.md
CHANGED
@@ -1,8 +1,7 @@
|
|
1
|
+
[![Gem Version](https://badge.fury.io/rb/salesforce_streamer.svg)](https://rubygems.org/gems/salesforce_streamer)
|
1
2
|
[![Build Status](https://travis-ci.org/RenoFi/salesforce_streamer.svg?branch=master)](https://travis-ci.org/RenoFi/salesforce_streamer)
|
2
3
|
|
3
|
-
|
4
|
-
|
5
|
-
# SalesforceStreamer
|
4
|
+
# salesforce_streamer
|
6
5
|
|
7
6
|
A wrapper around the Restforce Streaming API to receive real time updates from
|
8
7
|
your Salesforce instance with a built-in PushTopic manager.
|
@@ -153,7 +152,3 @@ Bug reports and pull requests are welcome on GitHub at https://github.com/renofi
|
|
153
152
|
## License
|
154
153
|
|
155
154
|
The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
|
156
|
-
|
157
|
-
## Code of Conduct
|
158
|
-
|
159
|
-
Everyone interacting in the SalesforceStreamer project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/renofi/salesforce_streamer/blob/master/CODE_OF_CONDUCT.md).
|
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: salesforce_streamer
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 1.1.
|
4
|
+
version: 1.1.3
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Scott Serok
|
@@ -9,7 +9,7 @@ authors:
|
|
9
9
|
autorequire:
|
10
10
|
bindir: exe
|
11
11
|
cert_chain: []
|
12
|
-
date: 2020-
|
12
|
+
date: 2020-04-03 00:00:00.000000000 Z
|
13
13
|
dependencies:
|
14
14
|
- !ruby/object:Gem::Dependency
|
15
15
|
name: faye
|
@@ -150,7 +150,6 @@ files:
|
|
150
150
|
- ".gitignore"
|
151
151
|
- ".rspec"
|
152
152
|
- ".travis.yml"
|
153
|
-
- CODE_OF_CONDUCT.md
|
154
153
|
- Gemfile
|
155
154
|
- Gemfile.lock
|
156
155
|
- LICENSE.txt
|
@@ -195,7 +194,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
195
194
|
- !ruby/object:Gem::Version
|
196
195
|
version: '0'
|
197
196
|
requirements: []
|
198
|
-
rubygems_version: 3.
|
197
|
+
rubygems_version: 3.1.2
|
199
198
|
signing_key:
|
200
199
|
specification_version: 4
|
201
200
|
summary: A wrapper around the Restforce Streaming API with a built-in PushTopic manager.
|
data/CODE_OF_CONDUCT.md
DELETED
@@ -1,74 +0,0 @@
|
|
1
|
-
# Contributor Covenant Code of Conduct
|
2
|
-
|
3
|
-
## Our Pledge
|
4
|
-
|
5
|
-
In the interest of fostering an open and welcoming environment, we as
|
6
|
-
contributors and maintainers pledge to making participation in our project and
|
7
|
-
our community a harassment-free experience for everyone, regardless of age, body
|
8
|
-
size, disability, ethnicity, gender identity and expression, level of experience,
|
9
|
-
nationality, personal appearance, race, religion, or sexual identity and
|
10
|
-
orientation.
|
11
|
-
|
12
|
-
## Our Standards
|
13
|
-
|
14
|
-
Examples of behavior that contributes to creating a positive environment
|
15
|
-
include:
|
16
|
-
|
17
|
-
* Using welcoming and inclusive language
|
18
|
-
* Being respectful of differing viewpoints and experiences
|
19
|
-
* Gracefully accepting constructive criticism
|
20
|
-
* Focusing on what is best for the community
|
21
|
-
* Showing empathy towards other community members
|
22
|
-
|
23
|
-
Examples of unacceptable behavior by participants include:
|
24
|
-
|
25
|
-
* The use of sexualized language or imagery and unwelcome sexual attention or
|
26
|
-
advances
|
27
|
-
* Trolling, insulting/derogatory comments, and personal or political attacks
|
28
|
-
* Public or private harassment
|
29
|
-
* Publishing others' private information, such as a physical or electronic
|
30
|
-
address, without explicit permission
|
31
|
-
* Other conduct which could reasonably be considered inappropriate in a
|
32
|
-
professional setting
|
33
|
-
|
34
|
-
## Our Responsibilities
|
35
|
-
|
36
|
-
Project maintainers are responsible for clarifying the standards of acceptable
|
37
|
-
behavior and are expected to take appropriate and fair corrective action in
|
38
|
-
response to any instances of unacceptable behavior.
|
39
|
-
|
40
|
-
Project maintainers have the right and responsibility to remove, edit, or
|
41
|
-
reject comments, commits, code, wiki edits, issues, and other contributions
|
42
|
-
that are not aligned to this Code of Conduct, or to ban temporarily or
|
43
|
-
permanently any contributor for other behaviors that they deem inappropriate,
|
44
|
-
threatening, offensive, or harmful.
|
45
|
-
|
46
|
-
## Scope
|
47
|
-
|
48
|
-
This Code of Conduct applies both within project spaces and in public spaces
|
49
|
-
when an individual is representing the project or its community. Examples of
|
50
|
-
representing a project or community include using an official project e-mail
|
51
|
-
address, posting via an official social media account, or acting as an appointed
|
52
|
-
representative at an online or offline event. Representation of a project may be
|
53
|
-
further defined and clarified by project maintainers.
|
54
|
-
|
55
|
-
## Enforcement
|
56
|
-
|
57
|
-
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
58
|
-
reported by contacting the project team at scott@renofi.com. All
|
59
|
-
complaints will be reviewed and investigated and will result in a response that
|
60
|
-
is deemed necessary and appropriate to the circumstances. The project team is
|
61
|
-
obligated to maintain confidentiality with regard to the reporter of an incident.
|
62
|
-
Further details of specific enforcement policies may be posted separately.
|
63
|
-
|
64
|
-
Project maintainers who do not follow or enforce the Code of Conduct in good
|
65
|
-
faith may face temporary or permanent repercussions as determined by other
|
66
|
-
members of the project's leadership.
|
67
|
-
|
68
|
-
## Attribution
|
69
|
-
|
70
|
-
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
|
71
|
-
available at [http://contributor-covenant.org/version/1/4][version]
|
72
|
-
|
73
|
-
[homepage]: http://contributor-covenant.org
|
74
|
-
[version]: http://contributor-covenant.org/version/1/4/
|