enumpath 0.1.1 → 0.2.0

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.
data/CONTRIBUTING.md DELETED
@@ -1,91 +0,0 @@
1
- # Contributing
2
-
3
- Thanks for being interested in our project! We welcome [all kinds of contributions](https://opensource.guide/how-to-contribute/). There are a few things you should know before contributing to this repository:
4
-
5
- 1. All contributors must agree to our Contributor License Agreement before any merge requests will be accepted.
6
- 2. Please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.
7
- 3. Please note we have a code of conduct, please follow it in all your interactions with the project.
8
-
9
- ## Pull Request Process
10
-
11
- 1. Fork the repo.
12
- 2. Make sure the tests pass before you begin working.
13
- 3. Make your changes, with new passing tests. Follow the [Ruby Style Guide](https://github.com/rubocop-hq/ruby-style-guide).
14
- 4. Push to your fork. Write a [good commit message](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
15
- 5. Submit a [good pull request](https://blog.github.com/2015-01-21-how-to-write-the-perfect-pull-request/).
16
- 6. Others will give constructive feedback. This is a time for discussion and improvements, and making the necessary changes will be required before we can merge the contribution.
17
-
18
- ## Code of Conduct
19
-
20
- ### Our Pledge
21
-
22
- In the interest of fostering an open and welcoming environment, we as
23
- contributors and maintainers pledge to making participation in our project and
24
- our community a harassment-free experience for everyone, regardless of age, body
25
- size, disability, ethnicity, sex characteristics, gender identity and expression,
26
- level of experience, education, socio-economic status, nationality, personal
27
- appearance, race, religion, or sexual identity and orientation.
28
-
29
- ### Our Standards
30
-
31
- Examples of behavior that contributes to creating a positive environment
32
- include:
33
-
34
- * Using welcoming and inclusive language
35
- * Being respectful of differing viewpoints and experiences
36
- * Gracefully accepting constructive criticism
37
- * Focusing on what is best for the community
38
- * Showing empathy towards other community members
39
-
40
- Examples of unacceptable behavior by participants include:
41
-
42
- * The use of sexualized language or imagery and unwelcome sexual attention or
43
- advances
44
- * Trolling, insulting/derogatory comments, and personal or political attacks
45
- * Public or private harassment
46
- * Publishing others' private information, such as a physical or electronic
47
- address, without explicit permission
48
- * Other conduct which could reasonably be considered inappropriate in a
49
- professional setting
50
-
51
- ### Our Responsibilities
52
-
53
- Project maintainers are responsible for clarifying the standards of acceptable
54
- behavior and are expected to take appropriate and fair corrective action in
55
- response to any instances of unacceptable behavior.
56
-
57
- Project maintainers have the right and responsibility to remove, edit, or
58
- reject comments, commits, code, wiki edits, issues, and other contributions
59
- that are not aligned to this Code of Conduct, or to ban temporarily or
60
- permanently any contributor for other behaviors that they deem inappropriate,
61
- threatening, offensive, or harmful.
62
-
63
- ### Scope
64
-
65
- This Code of Conduct applies both within project spaces and in public spaces
66
- when an individual is representing the project or its community. Examples of
67
- representing a project or community include using an official project e-mail
68
- address, posting via an official social media account, or acting as an appointed
69
- representative at an online or offline event. Representation of a project may be
70
- further defined and clarified by project maintainers.
71
-
72
- ### Enforcement
73
-
74
- Instances of abusive, harassing, or otherwise unacceptable behavior may be
75
- reported by contacting the project team at [INSERT EMAIL ADDRESS]. All
76
- complaints will be reviewed and investigated and will result in a response that
77
- is deemed necessary and appropriate to the circumstances. The project team is
78
- obligated to maintain confidentiality with regard to the reporter of an incident.
79
- Further details of specific enforcement policies may be posted separately.
80
-
81
- Project maintainers who do not follow or enforce the Code of Conduct in good
82
- faith may face temporary or permanent repercussions as determined by other
83
- members of the project's leadership.
84
-
85
- ### Attribution
86
-
87
- This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
88
- available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
89
-
90
- [homepage]: https://www.contributor-covenant.org
91
- [version]: http://contributor-covenant.org/version/1/4/
data/Gemfile DELETED
@@ -1,6 +0,0 @@
1
- source "https://rubygems.org"
2
-
3
- git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
4
-
5
- # Specify your gem's dependencies in enumpath.gemspec
6
- gemspec
data/Gemfile.lock DELETED
@@ -1,56 +0,0 @@
1
- PATH
2
- remote: .
3
- specs:
4
- enumpath (0.1.1)
5
- mini_cache (~> 1.1.0)
6
- to_regexp (~> 0.2.1)
7
-
8
- GEM
9
- remote: https://rubygems.org/
10
- specs:
11
- benchmark-perf (0.2.1)
12
- byebug (10.0.2)
13
- coderay (1.1.2)
14
- diff-lcs (1.3)
15
- method_source (0.9.0)
16
- mini_cache (1.1.0)
17
- null-logger (0.1.5)
18
- pry (0.11.3)
19
- coderay (~> 1.1.0)
20
- method_source (~> 0.9.0)
21
- pry-byebug (3.6.0)
22
- byebug (~> 10.0)
23
- pry (~> 0.10)
24
- rake (12.3.1)
25
- rspec (3.8.0)
26
- rspec-core (~> 3.8.0)
27
- rspec-expectations (~> 3.8.0)
28
- rspec-mocks (~> 3.8.0)
29
- rspec-benchmark (0.3.0)
30
- benchmark-perf (~> 0.2.0)
31
- rspec (>= 3.0.0, < 4.0.0)
32
- rspec-core (3.8.0)
33
- rspec-support (~> 3.8.0)
34
- rspec-expectations (3.8.1)
35
- diff-lcs (>= 1.2.0, < 2.0)
36
- rspec-support (~> 3.8.0)
37
- rspec-mocks (3.8.0)
38
- diff-lcs (>= 1.2.0, < 2.0)
39
- rspec-support (~> 3.8.0)
40
- rspec-support (3.8.0)
41
- to_regexp (0.2.1)
42
-
43
- PLATFORMS
44
- ruby
45
-
46
- DEPENDENCIES
47
- bundler (~> 1.16)
48
- enumpath!
49
- null-logger (~> 0.1)
50
- pry-byebug (~> 3.6)
51
- rake (~> 12.3)
52
- rspec (~> 3.8)
53
- rspec-benchmark (~> 0.3.0)
54
-
55
- BUNDLED WITH
56
- 1.16.3
data/Rakefile DELETED
@@ -1,11 +0,0 @@
1
- require "bundler/gem_tasks"
2
- require "rspec/core/rake_task"
3
- require "yard"
4
-
5
- RSpec::Core::RakeTask.new(:spec)
6
-
7
- task :default => :spec
8
-
9
- YARD::Rake::YardocTask.new do |t|
10
- t.options = ['--no-private', '-', 'LICENSE']
11
- end
data/bin/console DELETED
@@ -1,14 +0,0 @@
1
- #!/usr/bin/env ruby
2
-
3
- require "bundler/setup"
4
- require "enumpath"
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
- # (If you use this, don't forget to add pry to your Gemfile!)
10
- # require "pry"
11
- # Pry.start
12
-
13
- require "irb"
14
- IRB.start(__FILE__)
data/bin/setup DELETED
@@ -1,8 +0,0 @@
1
- #!/usr/bin/env bash
2
- set -euo pipefail
3
- IFS=$'\n\t'
4
- set -vx
5
-
6
- bundle install
7
-
8
- # Do any other automated setup that you need to do here
data/enumpath.gemspec DELETED
@@ -1,42 +0,0 @@
1
-
2
- lib = File.expand_path('../lib', __FILE__)
3
- $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
4
- require 'enumpath/version'
5
-
6
- Gem::Specification.new do |spec|
7
- spec.name = 'enumpath'
8
- spec.version = Enumpath::VERSION
9
- spec.license = 'Apache-2.0'
10
- spec.summary = 'A JSONPath-compatible library for navigating nested Ruby objects using path expressions'
11
- spec.description = <<~EOF
12
- Enumpath is an implementation of the JSONPath spec for Ruby objects,
13
- plus some added sugar. It's like Ruby's native Enumerable#dig method,
14
- but fancier. It is designed for situations where you need to provide
15
- a dynamic way of describing a complex path through nested enumerable
16
- objects. This makes it exceptionally well suited for flexible ETL
17
- (Extract, Transform, Load) processes by allowing you to define paths
18
- through your data in a simple, easily readable, easily storable syntax.
19
- EOF
20
- spec.authors = ['Chris Bloom']
21
- spec.email = ['open-source@youearnedit.com', 'chrisbloom7@gmail.com']
22
-
23
- spec.files = `git ls-files -z`.split("\x0").reject do |f|
24
- f.match(%r{^(test|spec|features)/})
25
- end
26
- spec.require_paths = ['lib']
27
-
28
- spec.homepage = 'https://github.com/youearnedit/enumpath'
29
-
30
- # Enumerable#dig was added in Ruby 2.3.0
31
- spec.required_ruby_version = '>= 2.3.0'
32
-
33
- spec.add_dependency 'to_regexp', '~> 0.2.1'
34
- spec.add_dependency 'mini_cache', '~> 1.1.0'
35
-
36
- spec.add_development_dependency 'bundler', '~> 1.16'
37
- spec.add_development_dependency 'null-logger', '~> 0.1'
38
- spec.add_development_dependency 'pry-byebug', '~> 3.6'
39
- spec.add_development_dependency 'rake', '~> 12.3'
40
- spec.add_development_dependency 'rspec-benchmark', '~> 0.3.0'
41
- spec.add_development_dependency 'rspec', '~> 3.8'
42
- end