enumpath 0.1.2 → 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.
- checksums.yaml +4 -4
- data/README.md +171 -31
- data/lib/enumpath/operator/base.rb +26 -11
- data/lib/enumpath/path.rb +10 -3
- data/lib/enumpath/resolver/object_inspector.rb +70 -0
- data/lib/enumpath/resolver/property.rb +227 -8
- data/lib/enumpath/resolver/simple.rb +35 -1
- data/lib/enumpath/version.rb +1 -1
- data/lib/enumpath.rb +13 -2
- metadata +43 -46
- data/.github/ISSUE_TEMPLATE/bug_report.md +0 -38
- data/.github/ISSUE_TEMPLATE/feature_request.md +0 -20
- data/.github/workflows/greetings.yml +0 -13
- data/.github/workflows/rubocop-analysis.yml +0 -47
- data/.github/workflows/ruby.yml +0 -35
- data/.gitignore +0 -15
- data/.rspec +0 -3
- data/.rubocop.yml +0 -12
- data/.yardopts +0 -1
- data/CONTRIBUTING.md +0 -96
- data/Gemfile +0 -8
- data/Gemfile.lock +0 -61
- data/Rakefile +0 -13
- data/bin/console +0 -15
- data/bin/setup +0 -8
- data/enumpath.gemspec +0 -45
|
@@ -1,47 +0,0 @@
|
|
|
1
|
-
# pulled from repo
|
|
2
|
-
name: "Rubocop"
|
|
3
|
-
|
|
4
|
-
on:
|
|
5
|
-
push:
|
|
6
|
-
branches: [ master ]
|
|
7
|
-
pull_request:
|
|
8
|
-
# The branches below must be a subset of the branches above
|
|
9
|
-
branches: [ master ]
|
|
10
|
-
schedule:
|
|
11
|
-
- cron: '15 23 * * 6'
|
|
12
|
-
|
|
13
|
-
jobs:
|
|
14
|
-
rubocop:
|
|
15
|
-
runs-on: ubuntu-latest
|
|
16
|
-
strategy:
|
|
17
|
-
fail-fast: false
|
|
18
|
-
|
|
19
|
-
steps:
|
|
20
|
-
- name: Checkout repository
|
|
21
|
-
uses: actions/checkout@v2
|
|
22
|
-
|
|
23
|
-
# If running on a self-hosted runner, check it meets the requirements
|
|
24
|
-
# listed at https://github.com/ruby/setup-ruby#using-self-hosted-runners
|
|
25
|
-
- name: Set up Ruby
|
|
26
|
-
uses: ruby/setup-ruby@v1
|
|
27
|
-
with:
|
|
28
|
-
ruby-version: 2.6
|
|
29
|
-
|
|
30
|
-
# This step is not necessary if you add the gem to your Gemfile
|
|
31
|
-
- name: Install Code Scanning integration
|
|
32
|
-
run: bundle add code-scanning-rubocop --version 0.3.0 --skip-install
|
|
33
|
-
|
|
34
|
-
- name: Install dependencies
|
|
35
|
-
run: bundle install
|
|
36
|
-
|
|
37
|
-
- name: Rubocop run
|
|
38
|
-
run: |
|
|
39
|
-
bash -c "
|
|
40
|
-
bundle exec rubocop --enable-pending-cops --require code_scanning --format CodeScanning::SarifFormatter -o rubocop.sarif
|
|
41
|
-
[[ $? -ne 2 ]]
|
|
42
|
-
"
|
|
43
|
-
|
|
44
|
-
- name: Upload Sarif output
|
|
45
|
-
uses: github/codeql-action/upload-sarif@v1
|
|
46
|
-
with:
|
|
47
|
-
sarif_file: rubocop.sarif
|
data/.github/workflows/ruby.yml
DELETED
|
@@ -1,35 +0,0 @@
|
|
|
1
|
-
# This workflow uses actions that are not certified by GitHub.
|
|
2
|
-
# They are provided by a third-party and are governed by
|
|
3
|
-
# separate terms of service, privacy policy, and support
|
|
4
|
-
# documentation.
|
|
5
|
-
# This workflow will download a prebuilt Ruby version, install dependencies and run tests with Rake
|
|
6
|
-
# For more information see: https://github.com/marketplace/actions/setup-ruby-jruby-and-truffleruby
|
|
7
|
-
|
|
8
|
-
name: Ruby
|
|
9
|
-
|
|
10
|
-
on:
|
|
11
|
-
push:
|
|
12
|
-
branches: [ master ]
|
|
13
|
-
pull_request:
|
|
14
|
-
branches: [ master ]
|
|
15
|
-
|
|
16
|
-
jobs:
|
|
17
|
-
test:
|
|
18
|
-
|
|
19
|
-
runs-on: ubuntu-latest
|
|
20
|
-
strategy:
|
|
21
|
-
matrix:
|
|
22
|
-
ruby-version: ['2.6', '2.7', '3.0']
|
|
23
|
-
|
|
24
|
-
steps:
|
|
25
|
-
- uses: actions/checkout@v2
|
|
26
|
-
- name: Set up Ruby
|
|
27
|
-
# To automatically get bug fixes and new Ruby versions for ruby/setup-ruby,
|
|
28
|
-
# change this to (see https://github.com/ruby/setup-ruby#versioning):
|
|
29
|
-
# uses: ruby/setup-ruby@v1
|
|
30
|
-
uses: ruby/setup-ruby@473e4d8fe5dd94ee328fdfca9f8c9c7afc9dae5e
|
|
31
|
-
with:
|
|
32
|
-
ruby-version: ${{ matrix.ruby-version }}
|
|
33
|
-
bundler-cache: true # runs 'bundle install' and caches installed gems automatically
|
|
34
|
-
- name: Run tests
|
|
35
|
-
run: bundle exec rake
|
data/.gitignore
DELETED
data/.rspec
DELETED
data/.rubocop.yml
DELETED
data/.yardopts
DELETED
|
@@ -1 +0,0 @@
|
|
|
1
|
-
--no-private - LICENSE
|
data/CONTRIBUTING.md
DELETED
|
@@ -1,96 +0,0 @@
|
|
|
1
|
-
# Contributing
|
|
2
|
-
|
|
3
|
-
Thanks for being interested in improving Enumpath! We welcome [all kinds of contributions][how-to-contribute]. There are a couple of things you should know before contributing to this repository:
|
|
4
|
-
|
|
5
|
-
1. Unless your changes are related to an existing issue, please first open a new issue to discuss the changes you wish to make.
|
|
6
|
-
2. Please note we have a [code of conduct](#code-of-conduct), please follow it in all your interactions with the project.
|
|
7
|
-
3. Code quality is important to us! Please be prepared to to address all code quality comments, whether from a CI tool like Hound or directly from our maintainers, before we can accept your changes.
|
|
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][ruby-style-guide].
|
|
14
|
-
4. Push to your fork using a [good commit message][a-note-about-git-commit-messages].
|
|
15
|
-
5. Submit a [good pull request][how-to-write-the-perfect-pull-request] from your fork to our project.
|
|
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 [chrisbloom7/enumpath][enumpath-gh]. 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
|
-
[a-note-about-git-commit-messages]: https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
|
|
91
|
-
[enumpath-gh]: https://github.com/chrisbloom7/enumpath
|
|
92
|
-
[homepage]: https://www.contributor-covenant.org
|
|
93
|
-
[how-to-contribute]: https://opensource.guide/how-to-contribute/
|
|
94
|
-
[how-to-write-the-perfect-pull-request]: https://blog.github.com/2015-01-21-how-to-write-the-perfect-pull-request/
|
|
95
|
-
[ruby-style-guide]: https://github.com/rubocop-hq/ruby-style-guide
|
|
96
|
-
[version]: http://contributor-covenant.org/version/1/4/
|
data/Gemfile
DELETED
data/Gemfile.lock
DELETED
|
@@ -1,61 +0,0 @@
|
|
|
1
|
-
PATH
|
|
2
|
-
remote: .
|
|
3
|
-
specs:
|
|
4
|
-
enumpath (0.1.2)
|
|
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.4.4)
|
|
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.3)
|
|
25
|
-
rspec (3.10.0)
|
|
26
|
-
rspec-core (~> 3.10.0)
|
|
27
|
-
rspec-expectations (~> 3.10.0)
|
|
28
|
-
rspec-mocks (~> 3.10.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.10.1)
|
|
33
|
-
rspec-support (~> 3.10.0)
|
|
34
|
-
rspec-expectations (3.10.1)
|
|
35
|
-
diff-lcs (>= 1.2.0, < 2.0)
|
|
36
|
-
rspec-support (~> 3.10.0)
|
|
37
|
-
rspec-mocks (3.10.2)
|
|
38
|
-
diff-lcs (>= 1.2.0, < 2.0)
|
|
39
|
-
rspec-support (~> 3.10.0)
|
|
40
|
-
rspec-support (3.10.2)
|
|
41
|
-
rspec_junit_formatter (0.4.1)
|
|
42
|
-
rspec-core (>= 2, < 4, != 2.12.0)
|
|
43
|
-
to_regexp (0.2.1)
|
|
44
|
-
yard (0.9.26)
|
|
45
|
-
|
|
46
|
-
PLATFORMS
|
|
47
|
-
ruby
|
|
48
|
-
|
|
49
|
-
DEPENDENCIES
|
|
50
|
-
bundler (~> 2.1)
|
|
51
|
-
enumpath!
|
|
52
|
-
null-logger (~> 0.1)
|
|
53
|
-
pry-byebug (~> 3.6)
|
|
54
|
-
rake (~> 12.3)
|
|
55
|
-
rspec (~> 3.8)
|
|
56
|
-
rspec-benchmark (~> 0.3.0)
|
|
57
|
-
rspec_junit_formatter (~> 0.4)
|
|
58
|
-
yard (~> 0.9.26)
|
|
59
|
-
|
|
60
|
-
BUNDLED WITH
|
|
61
|
-
2.2.15
|
data/Rakefile
DELETED
|
@@ -1,13 +0,0 @@
|
|
|
1
|
-
# frozen_string_literal: true
|
|
2
|
-
|
|
3
|
-
require 'bundler/gem_tasks'
|
|
4
|
-
require 'rspec/core/rake_task'
|
|
5
|
-
require 'yard'
|
|
6
|
-
|
|
7
|
-
RSpec::Core::RakeTask.new(:spec)
|
|
8
|
-
|
|
9
|
-
task default: :spec
|
|
10
|
-
|
|
11
|
-
YARD::Rake::YardocTask.new do |t|
|
|
12
|
-
t.options = ['--no-private', '-', 'LICENSE']
|
|
13
|
-
end
|
data/bin/console
DELETED
|
@@ -1,15 +0,0 @@
|
|
|
1
|
-
#!/usr/bin/env ruby
|
|
2
|
-
# frozen_string_literal: true
|
|
3
|
-
|
|
4
|
-
require 'bundler/setup'
|
|
5
|
-
require 'enumpath'
|
|
6
|
-
|
|
7
|
-
# You can add fixtures and/or initialization code here to make experimenting
|
|
8
|
-
# with your gem easier. You can also use a different console, if you like.
|
|
9
|
-
|
|
10
|
-
# (If you use this, don't forget to add pry to your Gemfile!)
|
|
11
|
-
# require "pry"
|
|
12
|
-
# Pry.start
|
|
13
|
-
|
|
14
|
-
require 'irb'
|
|
15
|
-
IRB.start(__FILE__)
|
data/bin/setup
DELETED
data/enumpath.gemspec
DELETED
|
@@ -1,45 +0,0 @@
|
|
|
1
|
-
# frozen_string_literal: true
|
|
2
|
-
|
|
3
|
-
lib = File.expand_path('lib', __dir__)
|
|
4
|
-
$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
|
|
5
|
-
require 'enumpath/version'
|
|
6
|
-
|
|
7
|
-
Gem::Specification.new do |spec|
|
|
8
|
-
spec.name = 'enumpath'
|
|
9
|
-
spec.version = Enumpath::VERSION
|
|
10
|
-
spec.license = 'Apache-2.0'
|
|
11
|
-
spec.summary = 'A JSONPath-compatible library for navigating nested Ruby objects using path expressions'
|
|
12
|
-
spec.description = <<~DESC
|
|
13
|
-
Enumpath is an implementation of the JSONPath spec for Ruby objects,
|
|
14
|
-
plus some added sugar. It's like Ruby's native Enumerable#dig method,
|
|
15
|
-
but fancier. It is designed for situations where you need to provide
|
|
16
|
-
a dynamic way of describing a complex path through nested enumerable
|
|
17
|
-
objects. This makes it exceptionally well suited for flexible ETL
|
|
18
|
-
(Extract, Transform, Load) processes by allowing you to define paths
|
|
19
|
-
through your data in a simple, easily readable, easily storable syntax.
|
|
20
|
-
DESC
|
|
21
|
-
spec.authors = ['Chris Bloom']
|
|
22
|
-
spec.email = ['chrisbloom7@gmail.com']
|
|
23
|
-
|
|
24
|
-
spec.files = `git ls-files -z`.split("\x0").reject do |f|
|
|
25
|
-
f.match(%r{^(test|spec|features)/})
|
|
26
|
-
end
|
|
27
|
-
spec.require_paths = ['lib']
|
|
28
|
-
|
|
29
|
-
spec.homepage = 'https://github.com/chrisbloom7/enumpath'
|
|
30
|
-
|
|
31
|
-
# Enumerable#dig was added in Ruby 2.3.0
|
|
32
|
-
spec.required_ruby_version = '>= 2.3.0'
|
|
33
|
-
|
|
34
|
-
spec.add_dependency 'mini_cache', '~> 1.1.0'
|
|
35
|
-
spec.add_dependency 'to_regexp', '~> 0.2.1'
|
|
36
|
-
|
|
37
|
-
spec.add_development_dependency 'bundler', '~> 2.1'
|
|
38
|
-
spec.add_development_dependency 'null-logger', '~> 0.1'
|
|
39
|
-
spec.add_development_dependency 'pry-byebug', '~> 3.6'
|
|
40
|
-
spec.add_development_dependency 'rake', '~> 12.3'
|
|
41
|
-
spec.add_development_dependency 'rspec', '~> 3.8'
|
|
42
|
-
spec.add_development_dependency 'rspec-benchmark', '~> 0.3.0'
|
|
43
|
-
spec.add_development_dependency 'rspec_junit_formatter', '~> 0.4'
|
|
44
|
-
spec.add_development_dependency 'yard', '~> 0.9.26'
|
|
45
|
-
end
|