data_set 1.0.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +7 -0
- data/.gitignore +40 -0
- data/.hound.yml +62 -0
- data/.rspec +3 -0
- data/.rubocop.yml +2 -0
- data/CODE_OF_CONDUCT.md +74 -0
- data/Gemfile +4 -0
- data/LICENSE.txt +21 -0
- data/README.md +146 -0
- data/Rakefile +31 -0
- data/bin/console +13 -0
- data/bin/setup +8 -0
- data/data_set.gemspec +37 -0
- data/lib/data_set/data_accessor.rb +31 -0
- data/lib/data_set/data_element.rb +11 -0
- data/lib/data_set/version.rb +3 -0
- data/lib/data_set.rb +18 -0
- metadata +146 -0
checksums.yaml
ADDED
@@ -0,0 +1,7 @@
|
|
1
|
+
---
|
2
|
+
SHA1:
|
3
|
+
metadata.gz: 1ac070118f4ee9038a536c47001afdad19075b20
|
4
|
+
data.tar.gz: 15df8ee5fc9210d01d122108d9d2f5db9074ef5a
|
5
|
+
SHA512:
|
6
|
+
metadata.gz: 08b5bfb4f398f665d8e8f3ebc7ecf8466489438a415d5e8823d04c8a39b8f72c724afca5c46ce5976116a6b75c3885a3d2bb263b343e265e55a27bb0c07df22b
|
7
|
+
data.tar.gz: 4bc6833d7258bb5ea04805e459a571f226068a996b88f2217493e375a05b0b6a04193e1cdadbb7f0822f37833e3955dd0bef25cb159c3885757297ca895bde18
|
data/.gitignore
ADDED
@@ -0,0 +1,40 @@
|
|
1
|
+
# Ruby-Specific
|
2
|
+
|
3
|
+
/.bundle/
|
4
|
+
/.yardoc
|
5
|
+
/Gemfile.lock
|
6
|
+
/_yardoc/
|
7
|
+
|
8
|
+
# Ouput-Specific
|
9
|
+
|
10
|
+
/coverage/
|
11
|
+
/doc/
|
12
|
+
/pkg/
|
13
|
+
/spec/reports/
|
14
|
+
/tmp/
|
15
|
+
*.log
|
16
|
+
*.tmp
|
17
|
+
*.swp
|
18
|
+
*.bak
|
19
|
+
|
20
|
+
# IDE-Specific
|
21
|
+
|
22
|
+
.idea
|
23
|
+
.settings
|
24
|
+
.project
|
25
|
+
.classpath
|
26
|
+
*.iws
|
27
|
+
|
28
|
+
# Windows-Specific
|
29
|
+
|
30
|
+
Thumbs.db
|
31
|
+
|
32
|
+
# Mac OS-Specific
|
33
|
+
|
34
|
+
*.DS_Store
|
35
|
+
._*
|
36
|
+
|
37
|
+
# Linux-Specific
|
38
|
+
|
39
|
+
.directory
|
40
|
+
.Trash-*
|
data/.hound.yml
ADDED
@@ -0,0 +1,62 @@
|
|
1
|
+
AllCops:
|
2
|
+
Exclude:
|
3
|
+
- data_set.gemspec
|
4
|
+
- test/*.rb
|
5
|
+
- spec/**/*
|
6
|
+
|
7
|
+
# Removing need for frozen string literal comment.
|
8
|
+
Style/FrozenStringLiteralComment:
|
9
|
+
Enabled: false
|
10
|
+
|
11
|
+
# Removing the preference for string single quotes.
|
12
|
+
Style/StringLiterals:
|
13
|
+
Enabled: false
|
14
|
+
|
15
|
+
# Missing top-level module documentation comment.
|
16
|
+
Style/Documentation:
|
17
|
+
Enabled: false
|
18
|
+
|
19
|
+
# Prefer reduce over inject.
|
20
|
+
Style/CollectionMethods:
|
21
|
+
PreferredMethods:
|
22
|
+
reduce: 'inject'
|
23
|
+
|
24
|
+
# Use each_with_object instead of inject.
|
25
|
+
Style/EachWithObject:
|
26
|
+
Enabled: false
|
27
|
+
|
28
|
+
# Prefer fail over raise.
|
29
|
+
Style/SignalException:
|
30
|
+
Enabled: false
|
31
|
+
|
32
|
+
# This never works for validations.
|
33
|
+
Style/AlignHash:
|
34
|
+
EnforcedLastArgumentHashStyle: ignore_implicit
|
35
|
+
|
36
|
+
# Align multi-line params with previous line.
|
37
|
+
Style/AlignParameters:
|
38
|
+
EnforcedStyle: with_fixed_indentation
|
39
|
+
|
40
|
+
# Indent `when` clause one step from `case`.
|
41
|
+
Style/CaseIndentation:
|
42
|
+
IndentOneStep: true
|
43
|
+
|
44
|
+
# Don't force bad var names for reduce/inject loops.
|
45
|
+
Style/SingleLineBlockParams:
|
46
|
+
Enabled: false
|
47
|
+
|
48
|
+
# For method chains, keep the dot with the method name.
|
49
|
+
Style/DotPosition:
|
50
|
+
EnforcedStyle: leading
|
51
|
+
|
52
|
+
# Stop nesting so hard.
|
53
|
+
Metrics/BlockNesting:
|
54
|
+
Max: 2
|
55
|
+
|
56
|
+
# Encourage short methods.
|
57
|
+
Metrics/MethodLength:
|
58
|
+
Max: 10
|
59
|
+
|
60
|
+
# Encourage fewer parameters.
|
61
|
+
Metrics/ParameterLists:
|
62
|
+
Max: 4
|
data/.rspec
ADDED
data/.rubocop.yml
ADDED
data/CODE_OF_CONDUCT.md
ADDED
@@ -0,0 +1,74 @@
|
|
1
|
+
# Contributor Covenant Code of Conduct
|
2
|
+
|
3
|
+
## Our Pledge
|
4
|
+
|
5
|
+
In the interest of fostering an open and welcoming environment, we as
|
6
|
+
contributors and maintainers pledge to making participation in our project and
|
7
|
+
our community a harassment-free experience for everyone, regardless of age, body
|
8
|
+
size, disability, ethnicity, gender identity and expression, level of experience,
|
9
|
+
nationality, personal appearance, race, religion, or sexual identity and
|
10
|
+
orientation.
|
11
|
+
|
12
|
+
## Our Standards
|
13
|
+
|
14
|
+
Examples of behavior that contributes to creating a positive environment
|
15
|
+
include:
|
16
|
+
|
17
|
+
* Using welcoming and inclusive language
|
18
|
+
* Being respectful of differing viewpoints and experiences
|
19
|
+
* Gracefully accepting constructive criticism
|
20
|
+
* Focusing on what is best for the community
|
21
|
+
* Showing empathy towards other community members
|
22
|
+
|
23
|
+
Examples of unacceptable behavior by participants include:
|
24
|
+
|
25
|
+
* The use of sexualized language or imagery and unwelcome sexual attention or
|
26
|
+
advances
|
27
|
+
* Trolling, insulting/derogatory comments, and personal or political attacks
|
28
|
+
* Public or private harassment
|
29
|
+
* Publishing others' private information, such as a physical or electronic
|
30
|
+
address, without explicit permission
|
31
|
+
* Other conduct which could reasonably be considered inappropriate in a
|
32
|
+
professional setting
|
33
|
+
|
34
|
+
## Our Responsibilities
|
35
|
+
|
36
|
+
Project maintainers are responsible for clarifying the standards of acceptable
|
37
|
+
behavior and are expected to take appropriate and fair corrective action in
|
38
|
+
response to any instances of unacceptable behavior.
|
39
|
+
|
40
|
+
Project maintainers have the right and responsibility to remove, edit, or
|
41
|
+
reject comments, commits, code, wiki edits, issues, and other contributions
|
42
|
+
that are not aligned to this Code of Conduct, or to ban temporarily or
|
43
|
+
permanently any contributor for other behaviors that they deem inappropriate,
|
44
|
+
threatening, offensive, or harmful.
|
45
|
+
|
46
|
+
## Scope
|
47
|
+
|
48
|
+
This Code of Conduct applies both within project spaces and in public spaces
|
49
|
+
when an individual is representing the project or its community. Examples of
|
50
|
+
representing a project or community include using an official project e-mail
|
51
|
+
address, posting via an official social media account, or acting as an appointed
|
52
|
+
representative at an online or offline event. Representation of a project may be
|
53
|
+
further defined and clarified by project maintainers.
|
54
|
+
|
55
|
+
## Enforcement
|
56
|
+
|
57
|
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
58
|
+
reported by contacting the project team at jeffnyman@gmail.com. All
|
59
|
+
complaints will be reviewed and investigated and will result in a response that
|
60
|
+
is deemed necessary and appropriate to the circumstances. The project team is
|
61
|
+
obligated to maintain confidentiality with regard to the reporter of an incident.
|
62
|
+
Further details of specific enforcement policies may be posted separately.
|
63
|
+
|
64
|
+
Project maintainers who do not follow or enforce the Code of Conduct in good
|
65
|
+
faith may face temporary or permanent repercussions as determined by other
|
66
|
+
members of the project's leadership.
|
67
|
+
|
68
|
+
## Attribution
|
69
|
+
|
70
|
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
|
71
|
+
available at [http://contributor-covenant.org/version/1/4][version]
|
72
|
+
|
73
|
+
[homepage]: http://contributor-covenant.org
|
74
|
+
[version]: http://contributor-covenant.org/version/1/4/
|
data/Gemfile
ADDED
data/LICENSE.txt
ADDED
@@ -0,0 +1,21 @@
|
|
1
|
+
The MIT License (MIT)
|
2
|
+
|
3
|
+
Copyright (c) 2016 Jeff Nyman
|
4
|
+
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
7
|
+
in the Software without restriction, including without limitation the rights
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
10
|
+
furnished to do so, subject to the following conditions:
|
11
|
+
|
12
|
+
The above copyright notice and this permission notice shall be included in
|
13
|
+
all copies or substantial portions of the Software.
|
14
|
+
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
21
|
+
THE SOFTWARE.
|
data/README.md
ADDED
@@ -0,0 +1,146 @@
|
|
1
|
+
# DataSet
|
2
|
+
|
3
|
+
[![Gem Version](https://badge.fury.io/rb/data_set.svg)](http://badge.fury.io/rb/data_set)
|
4
|
+
[![License](http://img.shields.io/badge/license-MIT-blue.svg)](https://github.com/jeffnyman/data_set/blob/master/LICENSE.txt)
|
5
|
+
|
6
|
+
[![Dependency Status](https://gemnasium.com/jeffnyman/data_set.png)](https://gemnasium.com/jeffnyman/data_set)
|
7
|
+
|
8
|
+
DataSet provides an easy mechanism to load up a set of data from a YAML file and then access that data by the structuring keys of the file. This provides an expressive way to retrieve data values.
|
9
|
+
|
10
|
+
## Installation
|
11
|
+
|
12
|
+
To get the latest stable release, add this line to your application's Gemfile:
|
13
|
+
|
14
|
+
```ruby
|
15
|
+
gem 'data_set'
|
16
|
+
```
|
17
|
+
|
18
|
+
And then include it in your bundle:
|
19
|
+
|
20
|
+
$ bundle
|
21
|
+
|
22
|
+
You can also install DataSet just as you would any other gem:
|
23
|
+
|
24
|
+
$ gem install data_set
|
25
|
+
|
26
|
+
## Usage
|
27
|
+
|
28
|
+
To use DataSet you can either specify a directory and file for loading or rely on the defaults. By default, DataSet will look for files in a `data` directory relative to the executing script. Also by default, DataSet will read a file named `default.yml` from that directory. These defaults apply if you don't specify anything to the contrary.
|
29
|
+
|
30
|
+
If you want to use a different directory you can simply set the directory like this:
|
31
|
+
|
32
|
+
```ruby
|
33
|
+
DataSet.data_path = 'config'
|
34
|
+
```
|
35
|
+
|
36
|
+
If you have a specific data file you want to load, you can specify it:
|
37
|
+
|
38
|
+
```ruby
|
39
|
+
DataSet.load('test_data.yml')
|
40
|
+
```
|
41
|
+
|
42
|
+
Calling the `load` method lets you begin to reference the data from that file. You can also specify a comma separated list of file names:
|
43
|
+
|
44
|
+
```ruby
|
45
|
+
DataSet.load('test_data.yml, accounts.yml, users.yml')
|
46
|
+
```
|
47
|
+
|
48
|
+
What DataSet is providing you is not just the loading of the file but a way to access the data directly by its name.
|
49
|
+
|
50
|
+
### Data Accessors
|
51
|
+
|
52
|
+
Consider a `test_data.yml` file with the following contents:
|
53
|
+
|
54
|
+
```yaml
|
55
|
+
home_url: 'https://veilus.herokuapp.com'
|
56
|
+
port: 9292
|
57
|
+
|
58
|
+
authentication:
|
59
|
+
username: admin
|
60
|
+
password: admin
|
61
|
+
|
62
|
+
first:
|
63
|
+
second:
|
64
|
+
third: testing
|
65
|
+
fourth: xyzzy
|
66
|
+
|
67
|
+
set_flag: true
|
68
|
+
cleared_flag: false
|
69
|
+
test_symbol: :marvel
|
70
|
+
```
|
71
|
+
|
72
|
+
Now you can load this file and begin calling methods on the DataSet that match the keys from the file.
|
73
|
+
|
74
|
+
```ruby
|
75
|
+
DataSet.load('test_data.yml')
|
76
|
+
|
77
|
+
puts DataSet.home_url
|
78
|
+
```
|
79
|
+
|
80
|
+
Here the last statement would return "https://veilus.herokuapp.com". Using this in context, I might do something like this:
|
81
|
+
|
82
|
+
```ruby
|
83
|
+
puts "#{DataSet.home_url}/planets"
|
84
|
+
```
|
85
|
+
|
86
|
+
You can also supply default values which will be returned if the property does not exist in the file. For example:
|
87
|
+
|
88
|
+
```ruby
|
89
|
+
puts "#{DataSet.home_url("http://localhost")}:#{DataSet.port}/planets"
|
90
|
+
```
|
91
|
+
|
92
|
+
Here `home_url` will be read from the file but, if it doesn't exist, the value provided to it will be used.
|
93
|
+
|
94
|
+
You can also access into the keys. For example, consider these statements:
|
95
|
+
|
96
|
+
```ruby
|
97
|
+
puts DataSet.authentication.username
|
98
|
+
puts DataSet.first.second.third
|
99
|
+
```
|
100
|
+
|
101
|
+
These statements would return the following based on the above data file:
|
102
|
+
|
103
|
+
```
|
104
|
+
admin
|
105
|
+
testing
|
106
|
+
```
|
107
|
+
|
108
|
+
You can also set an environment variable called `DATA_SET_FILE`. It's important to note that this is not a path. This is a file. The extent that this is useful depends on the context in which you slot it. Treating DataSet as an adjunct to an automated checking solution, for example, different machines that are using it could have different `DATA_SET_FILE` variables set. Or if using a tool like Cucumber, you could provide different profiles for execution like this:
|
109
|
+
|
110
|
+
```yaml
|
111
|
+
default: DATA_SET_FILE=test.yml
|
112
|
+
ci: DATA_SET_FILE=ci.yml
|
113
|
+
stage: DATA_SET_FILE=staging.yml
|
114
|
+
prod: DATA_SET_FILE=production.yml
|
115
|
+
```
|
116
|
+
|
117
|
+
This would allow the specific environment variable to be set conditionally based on execution.
|
118
|
+
|
119
|
+
## Development
|
120
|
+
|
121
|
+
After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec:all` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment. To install this gem onto your local machine, run `bundle exec rake install`.
|
122
|
+
|
123
|
+
## Contributing
|
124
|
+
|
125
|
+
Bug reports and pull requests are welcome on GitHub at [https://github.com/jeffnyman/data_set](https://github.com/jeffnyman/data_set). The testing ecosystem of Ruby is very large and this project is intended to be a welcoming arena for collaboration on yet another testing tool. As such, contributors are very much welcome but are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
|
126
|
+
|
127
|
+
To contribute to DataSet:
|
128
|
+
|
129
|
+
1. [Fork the project](http://gun.io/blog/how-to-github-fork-branch-and-pull-request/).
|
130
|
+
2. Create your feature branch. (`git checkout -b my-new-feature`)
|
131
|
+
3. Commit your changes. (`git commit -am 'new feature'`)
|
132
|
+
4. Push the branch. (`git push origin my-new-feature`)
|
133
|
+
5. Create a new [pull request](https://help.github.com/articles/using-pull-requests).
|
134
|
+
|
135
|
+
## Author
|
136
|
+
|
137
|
+
* [Jeff Nyman](http://testerstories.com)
|
138
|
+
|
139
|
+
## Credits
|
140
|
+
|
141
|
+
This code is loosely based upon the [FigNewton](https://github.com/cheezy/fig_newton) gem. I created a new version largely to avoid the name "FigNewton" as well as cleaning up the code and the documentation.
|
142
|
+
|
143
|
+
## License
|
144
|
+
|
145
|
+
DataSet is distributed under the [MIT](http://www.opensource.org/licenses/MIT) license.
|
146
|
+
See the [LICENSE](https://github.com/jeffnyman/data_set/blob/master/LICENSE.txt) file for details.
|
data/Rakefile
ADDED
@@ -0,0 +1,31 @@
|
|
1
|
+
#!/usr/bin/env rake
|
2
|
+
require "bundler/gem_tasks"
|
3
|
+
require "rdoc/task"
|
4
|
+
require "rubocop/rake_task"
|
5
|
+
require "rspec/core/rake_task"
|
6
|
+
|
7
|
+
RuboCop::RakeTask.new
|
8
|
+
|
9
|
+
namespace :spec do
|
10
|
+
desc 'Clean all generated reports'
|
11
|
+
task :clean do
|
12
|
+
system('rm -rf spec/reports')
|
13
|
+
end
|
14
|
+
|
15
|
+
RSpec::Core::RakeTask.new(all: :clean) do |config|
|
16
|
+
options = %w(--color)
|
17
|
+
options += %w(--format documentation)
|
18
|
+
options += %w(--format html --out spec/reports/unit-test-report.html)
|
19
|
+
|
20
|
+
config.rspec_opts = options
|
21
|
+
end
|
22
|
+
end
|
23
|
+
|
24
|
+
Rake::RDocTask.new do |rdoc|
|
25
|
+
rdoc.rdoc_dir = 'doc'
|
26
|
+
rdoc.main = 'README.md'
|
27
|
+
rdoc.title = "DataSet #{DataSet::VERSION}"
|
28
|
+
rdoc.rdoc_files.include('README*', 'lib/**/*.rb')
|
29
|
+
end
|
30
|
+
|
31
|
+
task default: ['spec:all', :rubocop]
|
data/bin/console
ADDED
@@ -0,0 +1,13 @@
|
|
1
|
+
#!/usr/bin/env ruby
|
2
|
+
|
3
|
+
require "bundler/setup"
|
4
|
+
require "data_set"
|
5
|
+
|
6
|
+
# You can add fixtures and/or initialization code here to make experimenting
|
7
|
+
# with your gem easier. You can also use a different console, if you like.
|
8
|
+
|
9
|
+
require "pry"
|
10
|
+
Pry.start
|
11
|
+
|
12
|
+
# require "irb"
|
13
|
+
# IRB.start
|
data/bin/setup
ADDED
data/data_set.gemspec
ADDED
@@ -0,0 +1,37 @@
|
|
1
|
+
# coding: utf-8
|
2
|
+
lib = File.expand_path('../lib', __FILE__)
|
3
|
+
$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
|
4
|
+
require 'data_set/version'
|
5
|
+
|
6
|
+
Gem::Specification.new do |spec|
|
7
|
+
spec.name = "data_set"
|
8
|
+
spec.version = DataSet::VERSION
|
9
|
+
spec.authors = ["Jeff Nyman"]
|
10
|
+
spec.email = ["jeffnyman@gmail.com"]
|
11
|
+
|
12
|
+
spec.summary = %q{Provides configuration specification and retrieval using YAML files.}
|
13
|
+
spec.description = %q{Provides configuration specification and retrieval using YAML files.}
|
14
|
+
spec.homepage = "https://github.com/jeffnyman/data_set"
|
15
|
+
spec.license = "MIT"
|
16
|
+
|
17
|
+
spec.files = `git ls-files -z`.split("\x0").reject do |f|
|
18
|
+
f.match(%r{^(test|spec|features)/})
|
19
|
+
end
|
20
|
+
spec.bindir = "exe"
|
21
|
+
spec.executables = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
|
22
|
+
spec.require_paths = ["lib"]
|
23
|
+
|
24
|
+
spec.add_development_dependency "bundler", "~> 1.13"
|
25
|
+
spec.add_development_dependency "rake", "~> 10.0"
|
26
|
+
spec.add_development_dependency "rspec", "~> 3.0"
|
27
|
+
spec.add_development_dependency "rubocop"
|
28
|
+
spec.add_development_dependency "pry"
|
29
|
+
|
30
|
+
spec.add_runtime_dependency "data_reader"
|
31
|
+
|
32
|
+
spec.post_install_message = %{
|
33
|
+
(::) (::) (::) (::) (::) (::) (::) (::) (::) (::) (::) (::)
|
34
|
+
DataSet #{DataSet::VERSION} has been installed.
|
35
|
+
(::) (::) (::) (::) (::) (::) (::) (::) (::) (::) (::) (::)
|
36
|
+
}
|
37
|
+
end
|
@@ -0,0 +1,31 @@
|
|
1
|
+
require "yaml"
|
2
|
+
|
3
|
+
module DataSet
|
4
|
+
module DataAccessor
|
5
|
+
def method_missing(*args, &block)
|
6
|
+
load_data_source unless @data_source
|
7
|
+
key = args.first
|
8
|
+
value = @data_source[key.to_s]
|
9
|
+
value = args[1] if value.nil?
|
10
|
+
super if value.nil?
|
11
|
+
value = DataSet::DataElement.new(value) unless type_known?(value)
|
12
|
+
value
|
13
|
+
end
|
14
|
+
|
15
|
+
def respond_to_missing?; end
|
16
|
+
|
17
|
+
def load_data_source
|
18
|
+
@data_source = nil
|
19
|
+
path = "#{data_path}/#{ENV['DATA_SET_FILE']}"
|
20
|
+
@yml = YAML.load_file path if ENV['DATA_SET_FILE']
|
21
|
+
DataSet.load('default.yml') if @data_set.nil?
|
22
|
+
end
|
23
|
+
|
24
|
+
private
|
25
|
+
|
26
|
+
def type_known?(value)
|
27
|
+
known_types = [String, Integer, TrueClass, FalseClass, Symbol]
|
28
|
+
known_types.any? { |type| value.is_a?(type) }
|
29
|
+
end
|
30
|
+
end
|
31
|
+
end
|
data/lib/data_set.rb
ADDED
@@ -0,0 +1,18 @@
|
|
1
|
+
require "data_set/version"
|
2
|
+
require "data_set/data_element"
|
3
|
+
require "data_set/data_accessor"
|
4
|
+
|
5
|
+
require "data_reader"
|
6
|
+
|
7
|
+
module DataSet
|
8
|
+
extend DataReader
|
9
|
+
extend DataSet::DataAccessor
|
10
|
+
|
11
|
+
class << self
|
12
|
+
attr_accessor :data
|
13
|
+
|
14
|
+
def default_data_path
|
15
|
+
'data'
|
16
|
+
end
|
17
|
+
end
|
18
|
+
end
|
metadata
ADDED
@@ -0,0 +1,146 @@
|
|
1
|
+
--- !ruby/object:Gem::Specification
|
2
|
+
name: data_set
|
3
|
+
version: !ruby/object:Gem::Version
|
4
|
+
version: 1.0.0
|
5
|
+
platform: ruby
|
6
|
+
authors:
|
7
|
+
- Jeff Nyman
|
8
|
+
autorequire:
|
9
|
+
bindir: exe
|
10
|
+
cert_chain: []
|
11
|
+
date: 2016-12-09 00:00:00.000000000 Z
|
12
|
+
dependencies:
|
13
|
+
- !ruby/object:Gem::Dependency
|
14
|
+
name: bundler
|
15
|
+
requirement: !ruby/object:Gem::Requirement
|
16
|
+
requirements:
|
17
|
+
- - "~>"
|
18
|
+
- !ruby/object:Gem::Version
|
19
|
+
version: '1.13'
|
20
|
+
type: :development
|
21
|
+
prerelease: false
|
22
|
+
version_requirements: !ruby/object:Gem::Requirement
|
23
|
+
requirements:
|
24
|
+
- - "~>"
|
25
|
+
- !ruby/object:Gem::Version
|
26
|
+
version: '1.13'
|
27
|
+
- !ruby/object:Gem::Dependency
|
28
|
+
name: rake
|
29
|
+
requirement: !ruby/object:Gem::Requirement
|
30
|
+
requirements:
|
31
|
+
- - "~>"
|
32
|
+
- !ruby/object:Gem::Version
|
33
|
+
version: '10.0'
|
34
|
+
type: :development
|
35
|
+
prerelease: false
|
36
|
+
version_requirements: !ruby/object:Gem::Requirement
|
37
|
+
requirements:
|
38
|
+
- - "~>"
|
39
|
+
- !ruby/object:Gem::Version
|
40
|
+
version: '10.0'
|
41
|
+
- !ruby/object:Gem::Dependency
|
42
|
+
name: rspec
|
43
|
+
requirement: !ruby/object:Gem::Requirement
|
44
|
+
requirements:
|
45
|
+
- - "~>"
|
46
|
+
- !ruby/object:Gem::Version
|
47
|
+
version: '3.0'
|
48
|
+
type: :development
|
49
|
+
prerelease: false
|
50
|
+
version_requirements: !ruby/object:Gem::Requirement
|
51
|
+
requirements:
|
52
|
+
- - "~>"
|
53
|
+
- !ruby/object:Gem::Version
|
54
|
+
version: '3.0'
|
55
|
+
- !ruby/object:Gem::Dependency
|
56
|
+
name: rubocop
|
57
|
+
requirement: !ruby/object:Gem::Requirement
|
58
|
+
requirements:
|
59
|
+
- - ">="
|
60
|
+
- !ruby/object:Gem::Version
|
61
|
+
version: '0'
|
62
|
+
type: :development
|
63
|
+
prerelease: false
|
64
|
+
version_requirements: !ruby/object:Gem::Requirement
|
65
|
+
requirements:
|
66
|
+
- - ">="
|
67
|
+
- !ruby/object:Gem::Version
|
68
|
+
version: '0'
|
69
|
+
- !ruby/object:Gem::Dependency
|
70
|
+
name: pry
|
71
|
+
requirement: !ruby/object:Gem::Requirement
|
72
|
+
requirements:
|
73
|
+
- - ">="
|
74
|
+
- !ruby/object:Gem::Version
|
75
|
+
version: '0'
|
76
|
+
type: :development
|
77
|
+
prerelease: false
|
78
|
+
version_requirements: !ruby/object:Gem::Requirement
|
79
|
+
requirements:
|
80
|
+
- - ">="
|
81
|
+
- !ruby/object:Gem::Version
|
82
|
+
version: '0'
|
83
|
+
- !ruby/object:Gem::Dependency
|
84
|
+
name: data_reader
|
85
|
+
requirement: !ruby/object:Gem::Requirement
|
86
|
+
requirements:
|
87
|
+
- - ">="
|
88
|
+
- !ruby/object:Gem::Version
|
89
|
+
version: '0'
|
90
|
+
type: :runtime
|
91
|
+
prerelease: false
|
92
|
+
version_requirements: !ruby/object:Gem::Requirement
|
93
|
+
requirements:
|
94
|
+
- - ">="
|
95
|
+
- !ruby/object:Gem::Version
|
96
|
+
version: '0'
|
97
|
+
description: Provides configuration specification and retrieval using YAML files.
|
98
|
+
email:
|
99
|
+
- jeffnyman@gmail.com
|
100
|
+
executables: []
|
101
|
+
extensions: []
|
102
|
+
extra_rdoc_files: []
|
103
|
+
files:
|
104
|
+
- ".gitignore"
|
105
|
+
- ".hound.yml"
|
106
|
+
- ".rspec"
|
107
|
+
- ".rubocop.yml"
|
108
|
+
- CODE_OF_CONDUCT.md
|
109
|
+
- Gemfile
|
110
|
+
- LICENSE.txt
|
111
|
+
- README.md
|
112
|
+
- Rakefile
|
113
|
+
- bin/console
|
114
|
+
- bin/setup
|
115
|
+
- data_set.gemspec
|
116
|
+
- lib/data_set.rb
|
117
|
+
- lib/data_set/data_accessor.rb
|
118
|
+
- lib/data_set/data_element.rb
|
119
|
+
- lib/data_set/version.rb
|
120
|
+
homepage: https://github.com/jeffnyman/data_set
|
121
|
+
licenses:
|
122
|
+
- MIT
|
123
|
+
metadata: {}
|
124
|
+
post_install_message: "\n(::) (::) (::) (::) (::) (::) (::) (::) (::) (::) (::) (::)\n
|
125
|
+
\ DataSet 1.0.0 has been installed.\n(::) (::) (::) (::) (::) (::) (::) (::) (::)
|
126
|
+
(::) (::) (::)\n "
|
127
|
+
rdoc_options: []
|
128
|
+
require_paths:
|
129
|
+
- lib
|
130
|
+
required_ruby_version: !ruby/object:Gem::Requirement
|
131
|
+
requirements:
|
132
|
+
- - ">="
|
133
|
+
- !ruby/object:Gem::Version
|
134
|
+
version: '0'
|
135
|
+
required_rubygems_version: !ruby/object:Gem::Requirement
|
136
|
+
requirements:
|
137
|
+
- - ">="
|
138
|
+
- !ruby/object:Gem::Version
|
139
|
+
version: '0'
|
140
|
+
requirements: []
|
141
|
+
rubyforge_project:
|
142
|
+
rubygems_version: 2.5.1
|
143
|
+
signing_key:
|
144
|
+
specification_version: 4
|
145
|
+
summary: Provides configuration specification and retrieval using YAML files.
|
146
|
+
test_files: []
|