yamlclean 0.1.0 → 0.1.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/Gemfile.lock +2 -2
- data/README.md +37 -0
- data/lib/yamlclean/version.rb +1 -1
- data/yamlclean.gemspec +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 9e311f3cd3e04000ded8310f7b003bfd02a81755
|
4
|
+
data.tar.gz: e51f949ef7cb759d1fa6c49bb3e7f249febe3497
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 83ecbfe0f212cdb20009f3a6b39e1b2c4fd88a5db75b20db75823efd3e3c80be806e5fed97b7a7eb6ceaace93830d5fc09dd4fbc2f42df934fc861279032edf6
|
7
|
+
data.tar.gz: 65bab2e705bac69f8b5042b22a2e99369df577f9c61233532467dcd47266cf6d353d15c075b43219744d0e145676d5ab2a3ac02983132587fffc2c003c15a217
|
data/Gemfile.lock
CHANGED
@@ -1,7 +1,8 @@
|
|
1
1
|
PATH
|
2
2
|
remote: .
|
3
3
|
specs:
|
4
|
-
yamlclean (0.1.
|
4
|
+
yamlclean (0.1.1)
|
5
|
+
ya2yaml
|
5
6
|
|
6
7
|
GEM
|
7
8
|
remote: https://rubygems.org/
|
@@ -17,7 +18,6 @@ DEPENDENCIES
|
|
17
18
|
bundler (~> 1.13)
|
18
19
|
minitest (~> 5.0)
|
19
20
|
rake (~> 10.0)
|
20
|
-
ya2yaml
|
21
21
|
yamlclean!
|
22
22
|
|
23
23
|
BUNDLED WITH
|
data/README.md
CHANGED
@@ -19,6 +19,43 @@ Usage
|
|
19
19
|
|
20
20
|
$> yamlclean input.yml > output.yml
|
21
21
|
|
22
|
+
What does it do?
|
23
|
+
----------------
|
24
|
+
|
25
|
+
The most significant change that this script makes is reformatting of multi-line strings.
|
26
|
+
|
27
|
+
It will convert this:
|
28
|
+
|
29
|
+
|
30
|
+
```yml
|
31
|
+
en_GB:
|
32
|
+
GroupImportForm:
|
33
|
+
Help2: '<div class="advanced">
|
34
|
+
|
35
|
+
<h4>Advanced usage</h4>
|
36
|
+
|
37
|
+
<ul><li>Allowed columns: <em>%s</em></li><li>Existing groups are matched by their unique <em>Code</em> value, and updated with any new values from the imported file</li><li>Group hierarchies can be created by using a <em>ParentCode</em> column.</li><li>Permission codes can be assigned by the <em>PermissionCode</em> column. Existing permission codes are not cleared.</li>
|
38
|
+
|
39
|
+
</ul>
|
40
|
+
|
41
|
+
</div>'
|
42
|
+
```
|
43
|
+
|
44
|
+
To this:
|
45
|
+
|
46
|
+
```yml
|
47
|
+
en_GB:
|
48
|
+
GroupImportForm:
|
49
|
+
Help2: |-
|
50
|
+
<div class="advanced">
|
51
|
+
<h4>Advanced usage</h4>
|
52
|
+
<ul><li>Allowed columns: <em>%s</em></li><li>Existing groups are matched by their unique <em>Code</em> value, and updated with any new values from the imported file</li><li>Group hierarchies can be created by using a <em>ParentCode</em> column.</li><li>Permission codes can be assigned by the <em>PermissionCode</em> column. Existing permission codes are not cleared.</li>
|
53
|
+
</ul>
|
54
|
+
</div>
|
55
|
+
```
|
56
|
+
|
57
|
+
This is important because many PHP and JavaScript yaml parsers won't parse the former syntax.
|
58
|
+
|
22
59
|
Contributing and development
|
23
60
|
----------------------------
|
24
61
|
|
data/lib/yamlclean/version.rb
CHANGED
data/yamlclean.gemspec
CHANGED
@@ -21,7 +21,7 @@ Gem::Specification.new do |spec|
|
|
21
21
|
spec.executables = [ "yamlclean" ]
|
22
22
|
spec.require_paths = ["lib"]
|
23
23
|
|
24
|
-
spec.
|
24
|
+
spec.add_dependency "ya2yaml"
|
25
25
|
|
26
26
|
spec.add_development_dependency "bundler", "~> 1.13"
|
27
27
|
spec.add_development_dependency "rake", "~> 10.0"
|
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: yamlclean
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.1.
|
4
|
+
version: 0.1.1
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Sam Minnee
|
@@ -17,7 +17,7 @@ dependencies:
|
|
17
17
|
- - '>='
|
18
18
|
- !ruby/object:Gem::Version
|
19
19
|
version: '0'
|
20
|
-
type: :
|
20
|
+
type: :runtime
|
21
21
|
prerelease: false
|
22
22
|
version_requirements: !ruby/object:Gem::Requirement
|
23
23
|
requirements:
|