blocks 3.0.0.rc9 → 3.0.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +2 -2
- data/bin/deploy_docs +1 -1
- data/docs/_includes/introduction.md +1 -1
- data/lib/blocks/version.rb +1 -1
- metadata +5 -5
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 2db13e9c6eec57ea11f32c6d9fd5de2674d3991a
|
|
4
|
+
data.tar.gz: 546e2c4294ff2e2e2d9722b11984b51b13d6d799
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: b28c7c12c2e3a3635b28255094ba2abe13ad4b35d7806d043e7f9717e48c04751b0354f019f944e2b01e1dd0c55e1d8a81f3b22c93f99036b86d9ea470e950a5
|
|
7
|
+
data.tar.gz: e23e4a7a45ad3ebf981332494583f2ff23dd7493c9dbf25e7165c67c92152024909e00b6ced6780ca0de2da6f4fd0ddd21be6bc41dbdeb8290a7cb9c5e7e7c13
|
data/README.md
CHANGED
|
@@ -13,7 +13,7 @@ It acts as:
|
|
|
13
13
|
|
|
14
14
|
Essentially, this all boils down to the following: Blocks makes it easy to define blocks of code that can be rendered either verbatim or with replacements and modifications at some later point in time.
|
|
15
15
|
|
|
16
|
-
[](https://travis-ci.org/hunterae/blocks)
|
|
17
17
|
|
|
18
18
|
## Usage
|
|
19
19
|
|
|
@@ -43,7 +43,7 @@ After checking out the repo, run `bundle install` (and possibly `gem install bun
|
|
|
43
43
|
|
|
44
44
|
The documentation is generated using [Jekyll](https://jekyllrb.com/) and hosted on the [Blocks gh-pages branch](https://github.com/hunterae/blocks/tree/gh-pages).
|
|
45
45
|
|
|
46
|
-
The static content is generated based on the source code within the [docs directory](https://github.com/hunterae/blocks/tree/
|
|
46
|
+
The static content is generated based on the source code within the [docs directory](https://github.com/hunterae/blocks/tree/master/docs).
|
|
47
47
|
|
|
48
48
|
To run the documentation locally or make changes for a corresponding pull request, follow the steps in the [Development Section above](#development). Then run `jekyll serve` and visit http://127.0.0.1:4000/blocks/.
|
|
49
49
|
|
data/bin/deploy_docs
CHANGED
|
@@ -1,2 +1,2 @@
|
|
|
1
1
|
#!/usr/bin/env bash
|
|
2
|
-
jgd -r
|
|
2
|
+
jgd -r master
|
|
@@ -15,4 +15,4 @@ It acts as:
|
|
|
15
15
|
|
|
16
16
|
Essentially, this all boils down to the following: Blocks makes it easy to define blocks of code that can be rendered either verbatim or with replacements and modifications at some later point in time.
|
|
17
17
|
|
|
18
|
-
[](https://travis-ci.org/hunterae/blocks)
|
data/lib/blocks/version.rb
CHANGED
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: blocks
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 3.0.0
|
|
4
|
+
version: 3.0.0
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Andrew Hunter
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: exe
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2017-09-
|
|
11
|
+
date: 2017-09-27 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: call_with_params
|
|
@@ -187,12 +187,12 @@ required_ruby_version: !ruby/object:Gem::Requirement
|
|
|
187
187
|
version: '0'
|
|
188
188
|
required_rubygems_version: !ruby/object:Gem::Requirement
|
|
189
189
|
requirements:
|
|
190
|
-
- - "
|
|
190
|
+
- - ">="
|
|
191
191
|
- !ruby/object:Gem::Version
|
|
192
|
-
version:
|
|
192
|
+
version: '0'
|
|
193
193
|
requirements: []
|
|
194
194
|
rubyforge_project:
|
|
195
|
-
rubygems_version: 2.6.
|
|
195
|
+
rubygems_version: 2.6.13
|
|
196
196
|
signing_key:
|
|
197
197
|
specification_version: 4
|
|
198
198
|
summary: Blocks gives you total control over how your blocks of code render.
|