guard-zeus 2.0.1.pre.alpha.pre.83 → 2.0.1.pre.alpha.pre.85
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 +8 -8
- data/README.md +11 -11
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,15 +1,15 @@
|
|
|
1
1
|
---
|
|
2
2
|
!binary "U0hBMQ==":
|
|
3
3
|
metadata.gz: !binary |-
|
|
4
|
-
|
|
4
|
+
NDAxNWJiMmY2YThmOTg2NTY2NGRhY2VjMmJkYzlmOGM3MmYwM2UxNg==
|
|
5
5
|
data.tar.gz: !binary |-
|
|
6
|
-
|
|
6
|
+
MGUxMjkyYzRjMDFiMjM3YThmNjg3MjZkNTE1N2FjNWZmM2ZmNzgzMg==
|
|
7
7
|
SHA512:
|
|
8
8
|
metadata.gz: !binary |-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
9
|
+
MDJjMDJlODFiZjU2NzM5NjNmZmI0MzVhNDJlODVkZDcyNGM4ZmQ0YjYyYjg4
|
|
10
|
+
OTU0ZDkyNGY1OGFkN2FjN2UwZTI1Mjc0OTE1ZDRlMzY3OGExMDQzYTc4Y2Rh
|
|
11
|
+
MTliZGQ4NGFjNzg4OGQzZTI5MDg3MzNkNmNmMmVkYmMxNTMyZmI=
|
|
12
12
|
data.tar.gz: !binary |-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
13
|
+
MGUyMzg3YjYyMDU1OGUyZDI0ZjY4OGU5MjRhOGJmMDhkZTkzZWEwZjA0ZTMz
|
|
14
|
+
OTU1NWU2N2U5YWY4ODM3MGYwNDYyZTNmNzJlZjEzMDY5NTk3ZjhjZTllZjNk
|
|
15
|
+
NTFiMTk0NDhiNDk0OGIyOTA1ZWEwMGM3ZDA1ZDdlMTY3NGM1ZGM=
|
data/README.md
CHANGED
|
@@ -35,17 +35,6 @@ 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
|
-
|
|
49
38
|
### Options
|
|
50
39
|
|
|
51
40
|
Available options:
|
|
@@ -58,6 +47,17 @@ Available options:
|
|
|
58
47
|
:run_all => true # Run all tests when hitting enter in guard
|
|
59
48
|
```
|
|
60
49
|
|
|
50
|
+
Known Issues
|
|
51
|
+
------------
|
|
52
|
+
|
|
53
|
+
There is a known issue when using guard-zues with pry, notably the zeus output appear on top of the pry console.
|
|
54
|
+
|
|
55
|
+
The workaround is to add the `cli` setting in your `Guardfile`, e.g.
|
|
56
|
+
|
|
57
|
+
```
|
|
58
|
+
guard 'zeus', cli: '> /dev/null' do
|
|
59
|
+
```
|
|
60
|
+
|
|
61
61
|
Development
|
|
62
62
|
-----------
|
|
63
63
|
|