ruby-satisfaction 0.6.2 → 0.6.3
Sign up to get free protection for your applications and to get access to all the features.
- data/README.markdown +12 -18
- data/lib/satisfaction/version.rb +1 -1
- metadata +3 -3
data/README.markdown
CHANGED
@@ -9,28 +9,22 @@ Please check our Web site for the latest documentation:
|
|
9
9
|
|
10
10
|
For questions, please visit the [Get Satisfaction API community][3]
|
11
11
|
|
12
|
-
|
13
|
-
|
14
|
-
|
15
|
-
If you use your Satisfaction object to get a person, then that object is scoped to that person.
|
16
|
-
|
17
|
-
For example:
|
18
|
-
|
19
|
-
sfn = Satisfaction.new
|
20
|
-
person = sfn.peson.get('jargon')
|
21
|
-
topics = sfn.topics.page(3, :order => 'recently_created') # Jargon's topics
|
12
|
+
Changelog
|
13
|
+
=========
|
22
14
|
|
23
|
-
|
24
|
-
top level. A simple workaround for now is to create a new Satisfaction object like so:
|
15
|
+
0.6.2
|
25
16
|
|
26
|
-
|
27
|
-
|
17
|
+
* Fixed known issue with scoping. Calling resource methods could potentially change scope for
|
18
|
+
other objects. For example:
|
28
19
|
|
29
|
-
|
30
|
-
|
20
|
+
sfn = Satisfaction.new
|
21
|
+
sfn2 = Satisfaction.new
|
22
|
+
person = sfn.peson.get('jargon')
|
23
|
+
topics = sfn.topics.page(3, :order => 'recently_created') # Jargon's topics
|
24
|
+
sfn2.topics # Also Jargon's topics
|
31
25
|
|
32
|
-
|
33
|
-
|
26
|
+
This now behaves as expected (where topics and sfn2.topics would be scoped to the set of all i
|
27
|
+
topics)
|
34
28
|
|
35
29
|
0.6.0
|
36
30
|
|
data/lib/satisfaction/version.rb
CHANGED
metadata
CHANGED
@@ -1,13 +1,13 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: ruby-satisfaction
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
hash:
|
4
|
+
hash: 1
|
5
5
|
prerelease: false
|
6
6
|
segments:
|
7
7
|
- 0
|
8
8
|
- 6
|
9
|
-
-
|
10
|
-
version: 0.6.
|
9
|
+
- 3
|
10
|
+
version: 0.6.3
|
11
11
|
platform: ruby
|
12
12
|
authors:
|
13
13
|
- Get Satisfaction
|