qc 0.6.0 → 0.6.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 5c22c9b2e8145ff0e939d3214848341e0782b3b2
-  data.tar.gz: 17b4c70a3a44993b71406d0994f45607734e70f4
+  metadata.gz: c64feb5cbc82a011016f90622f963b55b64a7c69
+  data.tar.gz: 60e392be59ad36bf92b350b045f116b1df7b08c7
 SHA512:
-  metadata.gz: 15e0d3601726a5df294eda0a402eec49e4667807e095dd03cfdb54050ed5c17097180dc6b3a90505c974372fd4ed85e32f0b2254c35c1b44f974f81446b6ce1a
-  data.tar.gz: c741d944839ae9b3f8d8f6abf86e7c7cc01d7ed9b79d9b6244b5703c142d90a09072d9aa64614111ee01a6cee3e02794f371353b72b6cacb35855e0201fc39fd
+  metadata.gz: d0c5969db8d962e646a8d38ffd98ca3d6c5166f41c92ccd7235aaf4061253f2fb0fb5c2834d77ea687defb510dff6895ad41ba3ae73dd423f33959047bbf681a
+  data.tar.gz: 06bbec814047319f0c0c6798b2e2b782229f5f750105aa29a86481e9081ab7b6036e125c387e61ae132da1c4cbbcf671d10752d0a93bbe072414a19325c0297a

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    qc (0.6.0)
+    qc (0.6.1)
       rest-client (~> 2.0.2)
       vcr (~> 3.0.3)
       webmock (~> 3.1.0)

data/README.md

@@ -26,7 +26,7 @@ When no command is provided, it will push your changes to QuantConnect, compile
 
 ```shell
 qc
-qc --open # To open the results in QuantConnect
+qc --open # To open the results in QuantConnect while running the backtest
 ```
 
 This is equivalent to executing `qc push`, `qc compile` and `qc backtest` in sequence.
@@ -39,7 +39,7 @@ qc [command]
 
 The supported commands are:
 
-| Command| description|
+| Command| Description|
 | -- | -- |
 | `qc login`| It will ask for the api credentials you can find in [your QuantConnect account page](https://www.quantconnect.com/account). They will be stored in `~/.qc`. You only need to login once. |  
 | `qc logout`| Logout from QuantConnect clearing the credentials stored locally.  |
@@ -58,7 +58,7 @@ qc --open
 qc backtest --open
 ```
 
-**This option only works on MacOS**. quantconnect.com currently doesn't offer an URL endpoint to open backtest results. In MacOS, it will use an Automator workflow that will open the project and show its latest results by simulating a click on the corresponding option. See [this discussion](https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/lean-engine/7AiEl3RVv38/PGnFQzBXAQAJ). 
+**This option only works in MacOS**. quantconnect.com currently doesn't offer an URL endpoint to open backtest results. In MacOS, it will use an Automator workflow that will open the project and show its latest results by simulating a click on the corresponding option. [See this discussion](https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/lean-engine/7AiEl3RVv38/PGnFQzBXAQAJ). 
 
 ## Development
 

data/lib/qc/command_runner.rb

@@ -257,7 +257,7 @@ module Qc
     end
 
     def changed_files
-      all_files = Dir["*.{#{project_settings.file_extensions}}"]
+      all_files = Dir["**/*.{#{project_settings.file_extensions}}"]
 
       return all_files unless project_settings.last_sync_at
 

data/lib/qc/version.rb

@@ -1,3 +1,3 @@
 module Qc
-  VERSION = "0.6.0"
+  VERSION = "0.6.1"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: qc
 version: !ruby/object:Gem::Version
-  version: 0.6.0
+  version: 0.6.1
 platform: ruby
 authors:
 - Jorge Manrubia
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-11-15 00:00:00.000000000 Z
+date: 2017-11-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rest-client