twingly-search 5.1.1 → 5.1.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: 60adc47513e35c4778e60e15ba44d38b4c2f229e
4
- data.tar.gz: 98023f64eab7ceb86066f3d06de920d9ebdb113d
3
+ metadata.gz: 3a75dac8aa30248ac63076961aed966d93bcb512
4
+ data.tar.gz: 1c777949aa160f64333d2b70873b6c1bc73fd3e9
5
5
  SHA512:
6
- metadata.gz: 80a9a299d9be055afb7acd3b96ab71b5abd140b0ea0e7764d48f39979ee45619218b13f5a3941a33b92abf4d4b611351703f81451537986d70cc54c7a063aabf
7
- data.tar.gz: b33ba8f7f5075ef854bfd0dbea4c586b15ee2c4df8e5775ad196b6802ab827e7d2737fb6bc43e064da3912ba4a8f4a8e505a93f3d7c3b738333ec4bdb466713b
6
+ metadata.gz: 6311e1a9faa3dabbd1f517370ab2e5efadb736bdbfc20fe7d93480b930ebeb35471eebfb0d006c7d95097c4e70d78d9ea4de20aed30706edfbcfb66ebe8ab4b6
7
+ data.tar.gz: 9fb8ec55a381bf78d234ec587e66893284187aee3a0960540a7a7f9675893218c35dae286df969f2595d0ca19510dcbf6f7b329f656fd216d82acde9d1b4e5a3
data/CHANGELOG.md CHANGED
@@ -1,5 +1,12 @@
1
1
  # Change Log
2
2
 
3
+ ## [v5.1.1](https://github.com/twingly/twingly-search-api-ruby/tree/v5.1.1) (2017-05-17)
4
+ [Full Changelog](https://github.com/twingly/twingly-search-api-ruby/compare/v5.1.0...v5.1.1)
5
+
6
+ **Merged pull requests:**
7
+
8
+ - Include timezone info for timestamps in search query [\#67](https://github.com/twingly/twingly-search-api-ruby/pull/67) ([roback](https://github.com/roback))
9
+
3
10
  ## [v5.1.0](https://github.com/twingly/twingly-search-api-ruby/tree/v5.1.0) (2017-05-09)
4
11
  [Full Changelog](https://github.com/twingly/twingly-search-api-ruby/compare/v5.0.1...v5.1.0)
5
12
 
@@ -65,13 +65,12 @@ module Twingly
65
65
  end
66
66
  end
67
67
 
68
- # TODO: Decide if a class or hash should be used...
69
68
  def parse_coordinates(element)
70
69
  return {} if element.children.empty?
71
70
 
72
71
  {
73
- latitude: element.at_xpath("latitude/text()"),
74
- longitude: element.at_xpath("longitude/text()"),
72
+ latitude: element.at_xpath("latitude").text.to_f,
73
+ longitude: element.at_xpath("longitude").text.to_f,
75
74
  }
76
75
  end
77
76
 
@@ -1,5 +1,5 @@
1
1
  module Twingly
2
2
  module Search
3
- VERSION = "5.1.1"
3
+ VERSION = "5.1.2"
4
4
  end
5
5
  end
@@ -0,0 +1,40 @@
1
+ <?xml version="1.0" encoding="UTF-8"?>
2
+ <twinglydata numberOfMatchesReturned="1" secondsElapsed="0.245" numberOfMatchesTotal="1" incompleteResult="false">
3
+ <post>
4
+ <id>7533026945919130930</id>
5
+ <author />
6
+ <url>http://odoo-community.org/blog/oca-news-1/post/code-sprint-in-louvain-la-neuve-oct-3-and-4-2016-64</url>
7
+ <title>Code Sprint in Louvain la Neuve (Oct 3 and 4, 2016)</title>
8
+ <text>All you wanted to know about the OCA code sprintbut were afraid to askWhen?The sprint starts on monday Oct 3, 9:00 and ends on tuesday Oct 4, 18:00.Where?The sprint will be hosted at the Ibis Hotel in Louvain la Neuve. The hotel is at a 15 min walk from the Louvain la Neuve railway station, and about the same distance from the Aula Magna where the Odoo Experience is being held later that week. If you want to drive there, the GPS coordinates are 50.673359, 4.607381.We booked the same room as for last year's sprint.What to bring?Bring your good spirit.Bring your laptop.Be sure to bring an adapter if your local power plugs don't match belgian power sockets. If you come in a group, it's a good idea to bring a multi plug to share the power socket.Having some paper and a pen is nice.You may want to bring an edible or drinkable delicacy from your home place to share with the other participants, but this is entirely optional.The hotel has a good WiFi installation. However, 60 persons trying to clone large projects from github simultaneously is a problem. Please get ready in advance, and clone the repositories before leaving for the sprint:https://github.com/odoo/odoo https://github.com/OCA/OCB the various OCA projects (hint : you can use the oca-clone-everything script from OCA/maintainer-tools)Do you have some kind of schedule?Sure!Both days should follow roughly the following plan:9h short start up speech, presentation of the rules and sprint tracks 9h30 - 12h30 code sprint 12h30 - ~14h lunch break 14h - 15h lightning talk track 14h - 17h code sprint 17h - 18h presentation of achievements by each sprint trackWhat will we eat?That's a very important question!The OCA will cover the costs of the lunches and coffee break, and the hotel restaurant is pretty good.There are no plans for dinners, but you will need to plan to handle this by yourself.If there are things you cannot eat for some reason, please send an email to alexandre.fayolle at camptocamp.com.What will be the sprint tracks?Based on the feedback received on the registration form here are the sprint tracks attendees are proposing to manage:Website CMS improvements (Simone Orsi) OpenDocument based reporting engine (Alexis de Lattre): there is one important topic I would like to achieve: decide which OpenDocument-based reporting engine we include in the OCA. Electronic invoicing (Alexis de Lattre) Refactor Geoengine by migrating it to OpenLayers 3 (oca/geospatial) (Yannick Vaucher): the work was started on Odoo 8 but is now stalled. Plus, Geoengine has seen some features this year making it greater, but on deprecated OpenLayers 2. I'd like to continue this refactoring and maybe get a first version without all the functionalities we go with OL2. Contributors stats gathering module (Maxime Chambreuil): OCA devs like contributors stats ! Getting to know the OCA Developpment Workflow (Robert Rottermann) document_sftp (Holger Brunn): I'd work on https://github.com/OCA/knowledge/tree/8.0/document_sftp. Or maybe implement a ssh server so that we can provide a shell with some odoo specific commands, so that we can write shell scripts doing odoo stuff while being authenticated with an ssh key Stocks logistics barcode scanning (Aaron Henriquez): Move to v9. Improve the Business Requirement set of modules (Eric Caudal) mobile community interface (Jairo Llopis): polish the interface and create an addon that leverages the power of CoffeScript for Odoo (similar to website_less, but for CS). Dockerizing the runbot (Alexandre Fayolle, Moisés López and Dave Lasley) mackma project (Frederik Kramer): work on www.mackma-project.eu an European Reasearch Project on Knowledge Mangement with Odoo setuptools-odoo (Stéphane Bidoul): eg update travis script to use it instead of oca-dependencies.txt, push to pypi, support Odoo 10, etcThere will probably be some tracks to perform code reviews, process pending PRs, port addons to newer Odoo releases.We will also have some lightning talks.Lightning talks? What's that?A lightning talk session is a 1h track where people get a 5min slot to show and tell about a topic of their choice. The time constraint is everything, 5min is all you get (and we have a stop watch), so be sure to rehease a bit. You will get an opportunity to propose talks at the last minute.Here's a list of talks participants proposed in the poll:How to document your module for all end users profit Improvements in bank-payment in v9 ? Odoo_Instances a toolset to setup and deoploy Odoo using docker document_sftp Inventory Revaluation module If I get the coffeescript toolchain working, then I'd love to present it in 5 minutes :) E-commerce alternative based on odoo and locootivecms. Voodoo a tool to develop and deploy easily odoo Devops Used at Vauxoo About new addons social/mail_tracking* Unit test odoo report base_custom_info and base_multi_image generic mixins web_timelineAny other question?ask it on the contributors mailing list !I'm looking forward to seeing you all in Louvain la Neuve!</text>
9
+ <languageCode>en</languageCode>
10
+ <locationCode>ru</locationCode>
11
+ <coordinates>
12
+ <latitude>49.1</latitude>
13
+ <longitude>10.75</longitude>
14
+ </coordinates>
15
+ <links>
16
+ <link>http://www.accorhotels.com/gb/hotel-2200-ibis-styles-meeting-center-louvain-la-neuve</link>
17
+ <link>http://www.openstreetmap.org/node/356183421#map=17/50.67292/4.61226</link>
18
+ <link>http://www.ahstatic.com/photos/2200_sm_02_p_1024x768.jpg</link>
19
+ <link>http://www.power-plugs-sockets.com/belgium</link>
20
+ <link>https://www.github.com/odoo/odoo</link>
21
+ <link>https://www.github.com/OCA/OCB</link>
22
+ <link>https://www.github.com/OCA/maintainer-tools</link>
23
+ <link>https://www.github.com/OCA/knowledge/tree/8.0/document_sftp</link>
24
+ <link>http://www.mackma-project.eu/</link>
25
+ </links>
26
+ <tags>
27
+ <tag>OCA News</tag>
28
+ </tags>
29
+ <images />
30
+ <indexedAt>2016-09-23T05:30:02Z</indexedAt>
31
+ <publishedAt>2017-05-28T15:01:48Z</publishedAt>
32
+ <reindexedAt>0001-01-01T00:00:00Z</reindexedAt>
33
+ <inlinksCount>0</inlinksCount>
34
+ <blogId>18224846301333517008</blogId>
35
+ <blogName>OCA News</blogName>
36
+ <blogUrl>https://odoo-community.org</blogUrl>
37
+ <blogRank>1</blogRank>
38
+ <authority>2</authority>
39
+ </post>
40
+ </twinglydata>
data/spec/parser_spec.rb CHANGED
@@ -283,6 +283,24 @@ describe Parser do
283
283
  end
284
284
  end
285
285
 
286
+ context "with a valid result containing coordinates" do
287
+ let(:fixture) { :valid_coordinates }
288
+
289
+ describe "#posts.first" do
290
+ subject(:post) { result.posts.first }
291
+ let(:expected_coordinates) do
292
+ {
293
+ latitude: 49.1,
294
+ longitude: 10.75,
295
+ }
296
+ end
297
+
298
+ describe "#coordinates" do
299
+ its(:coordinates) { should eq(expected_coordinates) }
300
+ end
301
+ end
302
+ end
303
+
286
304
  context "with a valid empty result" do
287
305
  let(:fixture) { :valid_empty }
288
306
 
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: twingly-search
3
3
  version: !ruby/object:Gem::Version
4
- version: 5.1.1
4
+ version: 5.1.2
5
5
  platform: ruby
6
6
  authors:
7
7
  - Twingly AB
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2017-05-17 00:00:00.000000000 Z
11
+ date: 2017-05-29 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: faraday
@@ -177,6 +177,7 @@ files:
177
177
  - spec/fixtures/service_unavailable_result.xml
178
178
  - spec/fixtures/unauthorized_api_key_result.xml
179
179
  - spec/fixtures/undefined_error_result.xml
180
+ - spec/fixtures/valid_coordinates_result.xml
180
181
  - spec/fixtures/valid_empty_result.xml
181
182
  - spec/fixtures/valid_links_result.xml
182
183
  - spec/fixtures/vcr_cassettes/livefeed_valid_request.yml
@@ -235,6 +236,7 @@ test_files:
235
236
  - spec/fixtures/service_unavailable_result.xml
236
237
  - spec/fixtures/unauthorized_api_key_result.xml
237
238
  - spec/fixtures/undefined_error_result.xml
239
+ - spec/fixtures/valid_coordinates_result.xml
238
240
  - spec/fixtures/valid_empty_result.xml
239
241
  - spec/fixtures/valid_links_result.xml
240
242
  - spec/fixtures/vcr_cassettes/livefeed_valid_request.yml