wcc-arena 0.3.0 → 0.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/lib/wcc/arena/group_query.rb +1 -1
- data/lib/wcc/arena/version.rb +1 -1
- data/spec/fixtures/person_group_list.xml +0 -1
- data/spec/wcc/arena/group_query_spec.rb +2 -2
- metadata +24 -24
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 1e29fcc958f30642c7e9fbf7f465620cab1e5806
|
4
|
+
data.tar.gz: 6316dcc30f5abe433bd8d6d11d0a0b891c22a1d9
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 1edd479615d7309c8e4e035baa65746760db7489387e345937a8701a0f9c4b4af3e7409a30b1cd314a015b43a80003fd986e321fa6782c98a56709e47e52eb20
|
7
|
+
data.tar.gz: 0fb29f14e52a839361fc6efbfed41d5df0e4fc4b86b70c678b80ffd79e4f44b5ecdf8c9587b768057af3adabaa917b54136f0077e6f84b0c67e0d034b4b8f32f
|
data/lib/wcc/arena/version.rb
CHANGED
@@ -52,9 +52,9 @@ describe WCC::Arena::GroupQuery do
|
|
52
52
|
end
|
53
53
|
end
|
54
54
|
|
55
|
-
it "
|
55
|
+
it "only includes active groups" do
|
56
56
|
subject.session.stub(:get) { fixture_response }
|
57
|
-
|
57
|
+
list.each { |l| expect(l).to be_active }
|
58
58
|
end
|
59
59
|
|
60
60
|
it "returns groups with unique IDs" do
|
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: wcc-arena
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.
|
4
|
+
version: 0.4.0
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Travis Petticrew
|
@@ -9,7 +9,7 @@ authors:
|
|
9
9
|
autorequire:
|
10
10
|
bindir: bin
|
11
11
|
cert_chain: []
|
12
|
-
date: 2015-12-
|
12
|
+
date: 2015-12-23 00:00:00.000000000 Z
|
13
13
|
dependencies:
|
14
14
|
- !ruby/object:Gem::Dependency
|
15
15
|
name: faraday
|
@@ -187,35 +187,35 @@ rubyforge_project:
|
|
187
187
|
rubygems_version: 2.4.2
|
188
188
|
signing_key:
|
189
189
|
specification_version: 4
|
190
|
-
summary:
|
191
|
-
system'
|
190
|
+
summary: "# WCC::Arena This gem provides wrappers to the Arena church management
|
191
|
+
system's API. This is an early version of the library, and has had limited testing
|
192
192
|
in real world environments. Use at your own risk! There are also bound to be a
|
193
|
-
few things that are specific to our configuration and version of Arena. This isn'
|
193
|
+
few things that are specific to our configuration and version of Arena. This isn't
|
194
194
|
intentional and we consider that a bug that we would like to fix. We would love
|
195
|
-
for this to be a fully featured way to interact with Arena'
|
196
|
-
this line to your application'
|
197
|
-
bundle Or install it yourself as: $ gem install wcc-arena ## Configuration
|
198
|
-
can configure the wcc-arena gem using the `WCC::Arena.configure` method. Here
|
199
|
-
an example configuration block: ```ruby WCC::Arena.configure do |arena| arena.username
|
200
|
-
= '
|
201
|
-
= '
|
202
|
-
library is currently a very thin layer over the Arena API. We plan to add
|
203
|
-
level interface layer that provides a better experience for the most common
|
204
|
-
cases. The library consists of Query classes and Mapper classes. The Query
|
205
|
-
handle calling the respective services and the Mapper classes handle binding
|
206
|
-
XML to Ruby objects. For full details on all available endpoints please see
|
207
|
-
code. Below are a few examples of some common queries. ```ruby person_query
|
208
|
-
"Travis") people = person_query.call
|
209
|
-
end ``` This will print the full names
|
210
|
-
"Travis". There are a ton of other attributes
|
211
|
-
Check them out on the [Person](https://github.com/watermarkchurch/wcc-arena/blob/master/lib/wcc/arena/person.rb)
|
195
|
+
for this to be a fully featured way to interact with Arena's API. ## Installation
|
196
|
+
\ Add this line to your application's Gemfile: gem 'wcc-arena' And then execute:
|
197
|
+
\ $ bundle Or install it yourself as: $ gem install wcc-arena ## Configuration
|
198
|
+
\ You can configure the wcc-arena gem using the `WCC::Arena.configure` method. Here
|
199
|
+
is an example configuration block: ```ruby WCC::Arena.configure do |arena| arena.username
|
200
|
+
= 'username' arena.password = 'password' arena.api_key = 'api_key' arena.api_secret
|
201
|
+
= 'api_secret' arena.api_url = 'https://arena-domain/api.svc/' end ``` ## Usage
|
202
|
+
\ The library is currently a very thin layer over the Arena API. We plan to add
|
203
|
+
a higher level interface layer that provides a better experience for the most common
|
204
|
+
use cases. The library consists of Query classes and Mapper classes. The Query
|
205
|
+
classes handle calling the respective services and the Mapper classes handle binding
|
206
|
+
the XML to Ruby objects. For full details on all available endpoints please see
|
207
|
+
the code. Below are a few examples of some common queries. ```ruby person_query
|
208
|
+
= WCC::Arena::PersonQuery.new.where(first_name: \"Travis\") people = person_query.call
|
209
|
+
people.each do |person| puts person.full_name end ``` This will print the full names
|
210
|
+
of all person records with the first name \"Travis\". There are a ton of other attributes
|
211
|
+
that are available on a Person record. Check them out on the [Person](https://github.com/watermarkchurch/wcc-arena/blob/master/lib/wcc/arena/person.rb)
|
212
212
|
model. You can also query tags (or Profiles as they are called under the hood).
|
213
213
|
To pull all top level Ministry tags run the following: ```ruby # This assumes that
|
214
214
|
your ministry tags have a type ID of 1. WCC::Arena::ProfileQuery.new(profile_type_id:
|
215
215
|
1).call.each do |tag| puts tag.name end ``` ## Contributing 1. Fork it 2. Create
|
216
216
|
your feature branch (`git checkout -b my-new-feature`) 3. Commit your changes (`git
|
217
|
-
commit -am '
|
218
|
-
5. Create new Pull Request
|
217
|
+
commit -am 'Add some feature'`) 4. Push to the branch (`git push origin my-new-feature`)
|
218
|
+
5. Create new Pull Request"
|
219
219
|
test_files:
|
220
220
|
- spec/fixtures/group_member_list.xml
|
221
221
|
- spec/fixtures/modify_result_failure.xml
|