guard-zeus 2.0.1.pre.alpha.pre.81 → 2.0.1.pre.alpha.pre.83
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +8 -8
- data/README.md +11 -0
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,15 +1,15 @@
|
|
|
1
1
|
---
|
|
2
2
|
!binary "U0hBMQ==":
|
|
3
3
|
metadata.gz: !binary |-
|
|
4
|
-
|
|
4
|
+
YjAxODk1ZWFkMjJmYzcwYTU5N2U0MTc2ZGE3Yzg4NTAzNmY4MWM4Yw==
|
|
5
5
|
data.tar.gz: !binary |-
|
|
6
|
-
|
|
6
|
+
NmZhMDJkNzg2YmQ4OGJmMGExOGIwZGUwNWY4YmFjNWViYzJiNWRmYQ==
|
|
7
7
|
SHA512:
|
|
8
8
|
metadata.gz: !binary |-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
9
|
+
MGFkYjU0ZjIzMTRjYmM1MmI5OWE1NWUwZTljYjUwMmJiZGQyMGRlMDU1Yzcw
|
|
10
|
+
ZDljOTFmNDk2Yzc4YjFkZDUxMTg2YWVjZWVkNzUxMmJkMTkwN2UwOTEyMDY4
|
|
11
|
+
Njg5MmI4MTA5MjQ5Yjg1ZmVlMzQ2OWZjY2RiN2IyYTgzNTEyMTU=
|
|
12
12
|
data.tar.gz: !binary |-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
13
|
+
ZTQ4NjJhZmFkMDA2ZGRmMTNhNzAzMWMxYWVjMWViZmY3YTU4MzcxZWEwOGM4
|
|
14
|
+
NzQ5MWM0MjkxM2I4YTFhMzkyMjU4ODA3NWI3NDlkODA2ODZhMTZmZWU1ZGVl
|
|
15
|
+
NWFkZjZhZTA4ZmUyYTdiNzJjMzI4NDQyYWE4YzY1Nzk4ZDE1ZjM=
|
data/README.md
CHANGED
|
@@ -35,6 +35,17 @@ Guardfile
|
|
|
35
35
|
|
|
36
36
|
Please read [Guard doc](https://github.com/guard/guard#readme) for more information about the Guardfile DSL.
|
|
37
37
|
|
|
38
|
+
Known Issues
|
|
39
|
+
------------
|
|
40
|
+
|
|
41
|
+
There is a known issue when using guard-zues with pry, notably the zeus output appear on top of the pry console.
|
|
42
|
+
|
|
43
|
+
The workaround is to add the `cli` setting in your `Guardfile`, e.g.
|
|
44
|
+
|
|
45
|
+
```
|
|
46
|
+
guard 'zeus', cli: '> /dev/null' do
|
|
47
|
+
```
|
|
48
|
+
|
|
38
49
|
### Options
|
|
39
50
|
|
|
40
51
|
Available options:
|