theme-juice 0.24.2 → 0.24.3

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 CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 208eac07b16a8376f463f6d027a6adedd69a5294
4
- data.tar.gz: 395dceecc0b25d3f955108e77125699c384e532a
3
+ metadata.gz: 8a9e5e8d2918da5c649b9a3ce22b964400561cd5
4
+ data.tar.gz: b683264274d48d6854493af39b94c0bfeb3a1704
5
5
  SHA512:
6
- metadata.gz: b1ef570cfb515933b7c53c6811fe9e7ccc0e341cfaf3412180797619bc912d58614137ee66ce4cc6444e75d101aa283e08ac283b0e88c53ebc617f8febef8784
7
- data.tar.gz: 9d0f7c4da768d5e10cd40862bafeec9aaf2c71781033294ad33d8aefceb0b422966fef5db5ee0015aaf4f1649c1c48d04958c8272295901c099fdd3379e0b297
6
+ metadata.gz: 1877fc5ad0fe261dcdf76bcc5aeee0114b4ae77afa4bda3ebd4b08c14190cf8a9d06599ba2eb042e3544947da8b0779ef3688858bcd729b343bbc05483091318
7
+ data.tar.gz: 1995177e016edbdb0bde953822f5f29960ad9ffcfa22d38614263ab9489b483bb1f7f45e5858442274ec84a8a68122cd8592255d6e0e835e0549fa30b4203a96
@@ -11,6 +11,9 @@ module ThemeJuice
11
11
  def command(cmd, *args)
12
12
  return if @project.no_config
13
13
 
14
+ args.map { |arg|
15
+ arg.reject! { |a| /^-/ =~ a } if arg.is_a?(Array) }
16
+
14
17
  commands.fetch("#{cmd}") {
15
18
  @io.error "Command '#{cmd}' not found in config", NotImplementedError }
16
19
  .each { |c| cmds = format_command(c, *args)
@@ -29,11 +29,11 @@ Force directory prefix for project in VM*
29
29
  .
30
30
  .TP
31
31
  \fB\-\-from\-path\fR, \fB\-\-in\-path\fR=\fIpath\fR
32
- Run Juicefile(5) commands from the passed path instead of the from current directory\.
32
+ Run Juicefile(5) commands from the passed path instead of from the current directory\.
33
33
  .
34
34
  .TP
35
35
  \fB\-\-from\-srv\fR, \fB\-\-in\-srv\fR=\fIpath\fR
36
- Run Juicefile(5) commands from the passed srv path instead of the from current directory when using the \fB\-\-inside\-vm\fR flag\.
36
+ Run Juicefile(5) commands from the passed srv path instead of from the current host directory path when using the \fB\-\-inside\-vm\fR flag\.
37
37
  .
38
38
  .TP
39
39
  \fB\-\-inside\-vm\fR, \fB\-\-in\-vm\fR
@@ -22,19 +22,20 @@ GLOBAL OPTIONS
22
22
  Force directory prefix for project in VM*
23
23
 
24
24
  --from-path, --in-path=path
25
- Run Juicefile(5) commands from the passed path instead of the
26
- from current directory.
25
+ Run Juicefile(5) commands from the passed path instead of from
26
+ the current directory.
27
27
 
28
28
  --from-srv, --in-srv=path
29
29
  Run Juicefile(5) commands from the passed srv path instead of
30
- the from current directory when using the --inside-vm flag.
30
+ from the current host directory path when using the --inside-vm
31
+ flag.
31
32
 
32
33
  --inside-vm, --in-vm
33
- Run Juicefile(5) commands from inside of the virtual machine
34
+ Run Juicefile(5) commands from inside of the virtual machine
34
35
  instead of your host machine.
35
36
 
36
37
  --yolo, --yes
37
- Say yes to anything and everything, and maybe even get a few
38
+ Say yes to anything and everything, and maybe even get a few
38
39
  surprises
39
40
 
40
41
  --boring
@@ -107,14 +108,14 @@ SECONDARY COMMANDS
107
108
  List all projects
108
109
 
109
110
  vm, vagrant, vvv=[command[,command]...]
110
- Manage development environment via vagrant(1). Commands are
111
- proxied to your Vagrant installation so that they can be run
111
+ Manage development environment via vagrant(1). Commands are
112
+ proxied to your Vagrant installation so that they can be run
112
113
  from any directory.
113
114
 
114
115
  CONFIG COMMANDS
115
- These run the corresponding command from your project's config file.
116
+ These run the corresponding command from your project's config file.
116
117
  They accept any number of arguments, since the behavior and handling of
117
- input is defined within the config file itself. Below are the commands
118
+ input is defined within the config file itself. Below are the commands
118
119
  defined within the Theme Juice starter template.
119
120
 
120
121
  install=[arg[,arg]...]
@@ -142,11 +143,11 @@ CONFIG COMMANDS
142
143
  Manage and run project tests
143
144
 
144
145
  CONFIG FILE
145
- A YAML Juicefile(5) configuration can be used to store commonly-used
146
- build scripts (and deploy(1) info), similar to npm(1) scripts. Each
147
- command block sequence can be mapped to an individual project's build
146
+ A YAML Juicefile(5) configuration can be used to store commonly-used
147
+ build scripts (and deploy(1) info), similar to npm(1) scripts. Each
148
+ command block sequence can be mapped to an individual project's build
148
149
  tool, allowing a streamlined set of commands to be used across multiple
149
- projects that utilize different tools. Below are descriptions for the
150
+ projects that utilize different tools. Below are descriptions for the
150
151
  default commands within the Theme Juice starter template's Juicefile.
151
152
 
152
153
  commands
@@ -176,7 +177,7 @@ CONFIG FILE
176
177
  commands.test
177
178
  Command used to manage and run project tests
178
179
 
179
- Placeholder arguments can be used within any command block sequence to
180
+ Placeholder arguments can be used within any command block sequence to
180
181
  allow splat or indexed arguments to be passed to the corresponding com-
181
182
  mand when executed.
182
183
 
@@ -186,8 +187,8 @@ CONFIG FILE
186
187
  %argN%, %argumentN%
187
188
  Where n is the argument index e.g. cmd %arg1% | cmd %arg2%
188
189
 
189
- When naming your configuration file, use the recommended Juicefile, or
190
- .tj.yaml naming convention. The raw filename regex matcher is below if
190
+ When naming your configuration file, use the recommended Juicefile, or
191
+ .tj.yaml naming convention. The raw filename regex matcher is below if
191
192
  you want to be a little different.
192
193
 
193
194
  /^(((\.)?(tj)|((J|j)uicefile))(\.y(a)?ml)?$)/
@@ -195,7 +196,7 @@ CONFIG FILE
195
196
  ENVIRONMENT
196
197
  All of the global options have a corresponding ENV variable that can be
197
198
  set to permanently use the specified value each time tj(1) is run. This
198
- is useful if you're using an alternate vagrant(1) box, or if you need
199
+ is useful if you're using an alternate vagrant(1) box, or if you need
199
200
  to disable certain features due to limited support i.e. on Windows.
200
201
 
201
202
  TJ_VM_BOX=repository
@@ -211,7 +212,7 @@ ENVIRONMENT
211
212
  Force directory prefix for project in VM
212
213
 
213
214
  TJ_YOLO=bool
214
- Say yes to anything and everything, and maybe even get a few
215
+ Say yes to anything and everything, and maybe even get a few
215
216
  surprises
216
217
 
217
218
  TJ_BORING=bool
@@ -1,5 +1,5 @@
1
1
  # encoding: UTF-8
2
2
 
3
3
  module ThemeJuice
4
- VERSION = "0.24.2"
4
+ VERSION = "0.24.3"
5
5
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: theme-juice
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.24.2
4
+ version: 0.24.3
5
5
  platform: ruby
6
6
  authors:
7
7
  - Ezekiel Gabrielse