endeca_on_demand 0.9.9 → 0.9.9.1
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.
- data/README.rdoc +9 -12
- data/endeca_on_demand.gemspec +1 -1
- data/lib/endeca_on_demand/version.rb +1 -1
- metadata +6 -6
data/README.rdoc
CHANGED
@@ -2,7 +2,7 @@
|
|
2
2
|
|
3
3
|
This Endeca On-Demand Web API gem will take a query-string and construct an XML query and send it to an hosted Endeca On-Demand Cluster. It will then parse the response and expose an API for using the response data.
|
4
4
|
|
5
|
-
NOTE: There are
|
5
|
+
NOTE: There are aspects of this that I am unable to test simply because the implementation I used to create it wasn't using all available options. Please, if you run into issues let me know so I can add anything thats missing, or feel free to add it yourself.
|
6
6
|
|
7
7
|
=== Features
|
8
8
|
|
@@ -110,7 +110,7 @@ Records:
|
|
110
110
|
puts "---------- END"
|
111
111
|
end
|
112
112
|
|
113
|
-
Breadcrumbs:
|
113
|
+
Breadcrumbs/Filtercrumbs:
|
114
114
|
|
115
115
|
@endeca.breadcrumbs.each do |crumb|
|
116
116
|
puts "---------- BEGIN CRUMB"
|
@@ -118,6 +118,12 @@ Breadcrumbs:
|
|
118
118
|
puts "---------- END"
|
119
119
|
end
|
120
120
|
|
121
|
+
@endeca.filtercrumbs.each do |crumb|
|
122
|
+
puts "---------- BEGIN CRUMB"
|
123
|
+
puts "CRUMB: #{crumb.inspect}"
|
124
|
+
puts "---------- END"
|
125
|
+
end
|
126
|
+
|
121
127
|
Dimensions:
|
122
128
|
|
123
129
|
@endeca.dimensions.each do |dimension|
|
@@ -138,14 +144,6 @@ Rules:
|
|
138
144
|
puts "RULE RECORDS: #{rule.records}"
|
139
145
|
puts "---------- END"
|
140
146
|
end
|
141
|
-
|
142
|
-
Filters:
|
143
|
-
|
144
|
-
@endeca.filters.each do |filter|
|
145
|
-
puts "---------- BEGIN FILTER"
|
146
|
-
puts "FILTER: #{filter.inspect}"
|
147
|
-
puts "---------- END"
|
148
|
-
end
|
149
147
|
|
150
148
|
Each object will have associated instance variables that will allow you directly call any value on that object:
|
151
149
|
|
@@ -161,8 +159,7 @@ Each object will have associated instance variables that will allow you directly
|
|
161
159
|
|
162
160
|
=== TODO
|
163
161
|
|
164
|
-
* More detail on breadcrumbs (and their suggested use as left nav filters)
|
165
|
-
* More on filters
|
162
|
+
* [complete] More detail on breadcrumbs (and their suggested use as left nav filters)
|
166
163
|
* Build in support for filters
|
167
164
|
* Add tests
|
168
165
|
* I don't have all the possible advanced parameters, so for now it only handles the default 'AggregationKey'
|
data/endeca_on_demand.gemspec
CHANGED
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: endeca_on_demand
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.9.9
|
4
|
+
version: 0.9.9.1
|
5
5
|
prerelease:
|
6
6
|
platform: ruby
|
7
7
|
authors:
|
@@ -12,8 +12,8 @@ cert_chain: []
|
|
12
12
|
date: 2011-09-07 00:00:00.000000000Z
|
13
13
|
dependencies:
|
14
14
|
- !ruby/object:Gem::Dependency
|
15
|
-
name:
|
16
|
-
requirement: &
|
15
|
+
name: nokogiri
|
16
|
+
requirement: &70172325736400 !ruby/object:Gem::Requirement
|
17
17
|
none: false
|
18
18
|
requirements:
|
19
19
|
- - ! '>='
|
@@ -21,10 +21,10 @@ dependencies:
|
|
21
21
|
version: '0'
|
22
22
|
type: :runtime
|
23
23
|
prerelease: false
|
24
|
-
version_requirements: *
|
24
|
+
version_requirements: *70172325736400
|
25
25
|
- !ruby/object:Gem::Dependency
|
26
26
|
name: rspec
|
27
|
-
requirement: &
|
27
|
+
requirement: &70172325704300 !ruby/object:Gem::Requirement
|
28
28
|
none: false
|
29
29
|
requirements:
|
30
30
|
- - ! '>='
|
@@ -32,7 +32,7 @@ dependencies:
|
|
32
32
|
version: '0'
|
33
33
|
type: :development
|
34
34
|
prerelease: false
|
35
|
-
version_requirements: *
|
35
|
+
version_requirements: *70172325704300
|
36
36
|
description: EndecaOnDemand will take a query-string and construct an XML query and
|
37
37
|
send it to an hosted Endeca On-Demand Cluster. It will then parse the response and
|
38
38
|
expose an API for using the response data.
|