yamlook 0.1.0 → 0.1.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.
Files changed (4) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +17 -0
  3. data/lib/yamlook/version.rb +1 -1
  4. metadata +2 -2
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 721149ad77c2d1122094c2861ebf1f4d0238dfe475c7849751468f804f94b5c9
4
- data.tar.gz: 5a9bfa6256d28b43c02f2b40ae3a700e3b085c289c7d74a857e3e7d070feb191
3
+ metadata.gz: d8d60c103a1ccc580ea4ef6e0d3e2f5f053caae8a43cf43938faa120b953a5c6
4
+ data.tar.gz: 7056f0a884fd99fc881360bd6c2945554699995546e2de3e81c73187613d4994
5
5
  SHA512:
6
- metadata.gz: 031f66fa62e1ddd557f663b085309576c8ebb62cfc671b3d979696b0e8df753598ead9e069ab322ef7631f5f35b3d14749776aa6757fb32079a4378e920b2c5d
7
- data.tar.gz: 110c6cd592fcb0594a5efbd5cb8243bd49b1d6ac1fbedd6e1dd7f8422e7bd8da804a22b9bbbbb905b291e73459a98090822adc65d5c942b7fa3a278a51b8faf8
6
+ metadata.gz: 1589f85031a782dc1e269d857f77f4b2ef686fb34823334cc0bf0a722bfc48545b69f8b121822e20855948bfd34180394743c691286bc63574ef47f9ff6bafdb
7
+ data.tar.gz: 76fedaacd5a13e16ef5d1feab2604c91b275047873e80e303242c9444cced2b04e2a51e3c77d3ddd9e1f8af8dac8b774122d0aecdd2e084edbd0aeb804026a9b
data/README.md CHANGED
@@ -1,5 +1,16 @@
1
1
  # Yamlook
2
2
 
3
+ Yamlook searches for dot-notated yaml keys occurrences in yaml files. It might be handy if you have localization
4
+ or deep configs and you don't know where one or another value comes from.
5
+
6
+ For instance you have such code:
7
+ ```
8
+ t("admin.marketing.reports.some_report.title"), some_report_path(format: "csv")
9
+ ```
10
+ Run `yamlook admin.marketing.reports.some_report.title` in terminal and it will show up all occurrences of that value
11
+ in your internationalization yaml files. If you have all the internationalization in one yaml file, you will likely
12
+ have to specify some root key as well, e.g. `yamlook en.admin.marketing.reports.some_report.title`.
13
+
3
14
  ## Installation
4
15
 
5
16
  ```
@@ -8,10 +19,16 @@ $ gem install yamlook
8
19
 
9
20
  ## Usage
10
21
 
22
+ Run yamlook in terminal with dot-notated yaml keys as argument:
11
23
  ```
12
24
  $ yamlook some.deep.key.in.you.yaml.file
13
25
  ```
14
26
 
27
+ ## Contributing
28
+
29
+ Bug reports and pull requests are welcome on GitHub at https://github.com/[sl4vr]/yamlook.
30
+
31
+
15
32
  ## License
16
33
 
17
34
  The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).
@@ -1,5 +1,5 @@
1
1
  # frozen_string_literal: true
2
2
 
3
3
  module Yamlook
4
- VERSION = '0.1.0'
4
+ VERSION = '0.1.1'
5
5
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: yamlook
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.0
4
+ version: 0.1.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Viacheslav Mefodin
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2020-09-22 00:00:00.000000000 Z
11
+ date: 2020-11-07 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: psych