guard-entangle 0.0.5.0 → 0.0.5.1
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 +4 -4
- data/README.md +1 -3
- data/lib/guard/entangle/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: e115d06bff0dc6c1bec8ce76c53f2f818c93a27f
|
|
4
|
+
data.tar.gz: 93bfff813e258a0af99b7fac146b0799e0378cb5
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 3a548f687fad9d3b4971522dec880008a731a61ff18c461af4c13171fa8b966a97ae9be1cd001c3fd5cbed7f3cf3d0ec6159b0ee91434ca045f8dee43f6d28b0
|
|
7
|
+
data.tar.gz: eb9001470265bf6c686744bea8009b299fafaca206f87f010f692ffe47d7b1bdbded089ac58f85092aef661ee31f8878fa7d042757a93582a50c59980b846599
|
data/README.md
CHANGED
|
@@ -8,8 +8,6 @@ Often you might have separate JavaScript files that need to be included into one
|
|
|
8
8
|
|
|
9
9
|
## Installation
|
|
10
10
|
|
|
11
|
-
NOTE: This is an innitial release - just to make sure the name isn't stolen now that it's on Github (I'm told this happens). There are a couple of Rpecs missing. It will be a full release once those files are added to this gem.
|
|
12
|
-
|
|
13
11
|
Add this line to your application's Gemfile:
|
|
14
12
|
|
|
15
13
|
gem 'guard-entangle'
|
|
@@ -45,7 +43,7 @@ When a single file is triggered, it will check if the file is a partial or not.
|
|
|
45
43
|
|
|
46
44
|
A partial is a file that is not meant to be complied on its own, but is included within another file. Guard-Entangle determines this by check if the file or folder has **_**
|
|
47
45
|
at the start of its name. For example a file named *_File1.js* will be considered to be a partial. Folders that start with _ will be skipped when runnign the run all command. All files within a partials folder should also start with an _.
|
|
48
|
-
|
|
46
|
+
|
|
49
47
|
If it is a partial, it will trigger the _run all_ command. If its not a partial, it will compile that file only. This is because partials don't get compiled on their own, but its their parent that needs to be compiled.
|
|
50
48
|
|
|
51
49
|
The _run all_ command will take all the file(s) in the input directory (that are not partials) and compile them into the output directory.
|