rarbg 1.4.0 → 2.0.0

data/.editorconfig

@@ -1,12 +0,0 @@
-root = true
-
-[*]
-charset = utf-8
-end_of_line = lf
-indent_size = 2
-indent_style = space
-insert_final_newline = true
-trim_trailing_whitespace = true
-
-[*.md]
-trim_trailing_whitespace = false

data/.github/CODEOWNERS

@@ -1,4 +0,0 @@
-# These owners will be the default owners for everything in the repo.
-# Unless a later match takes precedence, they will be requested for review
-# when someone opens a pull request.
-* @epistrephein

data/.github/ISSUE_TEMPLATE/BUG_REPORT.md

@@ -1,25 +0,0 @@
----
-name: Bug Report
-about: Report something that isn't working as expected.
-
----
-
-## Bug description
-A clear and concise description of what the bug is, what you expected to happen
-and what happened instead.
-
-## Steps to reproduce
-1. Instantiate object...
-2. Call method...
-3. Error is raised...
-
-## Environment
-- Gem version:
-- Ruby version:
-- OS and version:
-
-## Logs
-If applicable, add logs or screenshots to help explain your problem.
-
-## Additional context
-Add any other context about the problem here.

data/.github/ISSUE_TEMPLATE/FEATURE_REQUEST.md

@@ -1,18 +0,0 @@
----
-name: Feature request
-about: Suggest an idea for this project.
-
----
-
-## Feature description
-A clear and concise description of what problem you're trying to solve and what
-you'd want to happen.
-
-## Possible implementations
-If possible, suggest a way to add this feature.
-
-## Alternatives considered
-A description of any alternative solutions or features you've considered.
-
-## Additional context
-Add any other context about the feature here.

data/.github/PULL_REQUEST_TEMPLATE.md

@@ -1,14 +0,0 @@
-## Pull Request description
-A clear and concise explanation of what changes your PR introduces and why this was needed.
-
-## Pull Request checklist
-
-- [ ] My code is a **bug fix** (non-breaking change which fixes an issue)
-- [ ] My code is a **new feature** (non-breaking change which adds functionality)
-- [ ] My code introduces a **breaking change** (fix or feature that would break existing functionality)
-- [ ] My code follows the code style of this project
-- [ ] My change requires a change to the documentation
-- [ ] I have updated the documentation accordingly
-- [ ] I have included the CHANGELOG entry for the changes
-- [ ] I have added tests to cover my changes
-- [ ] All new and existing tests passed

data/.gitignore

@@ -1,44 +0,0 @@
-*.gem
-*.rbc
-/.config
-/coverage/
-/InstalledFiles
-/pkg/
-/test/tmp/
-/test/version_tmp/
-/tmp/
-
-# Version specifiers
-Gemfile.lock
-gems.locked
-.ruby-version
-.ruby-gemset
-
-# Environment normalization
-/.bundle/
-/lib/bundler/man/
-
-# RSpec
-/spec/reports/
-/spec/examples.txt
-.rspec_status
-
-# Documentation cache
-/.yardoc/
-/_yardoc/
-/doc/
-/rdoc/
-
-# Logs
-*.log
-*.log.[0-9]*
-
-# Pry
-.pryrc
-.pry_history
-
-# RVM
-.rvmrc
-
-# Project specific
-apidocs_v2.txt

data/.hound.yml

@@ -1,5 +0,0 @@
-fail_on_violations: true
-
-rubocop:
-  config_file: .rubocop.yml
-  version: 0.71.0

data/.rspec

@@ -1,4 +0,0 @@
---color
---format documentation
---order random
---require spec_helper

data/.rubocop.yml

@@ -1,36 +0,0 @@
-AllCops:
-  TargetRubyVersion: 2.3
-  DisplayCopNames: true
-  DisplayStyleGuide: true
-
-Gemspec/RequiredRubyVersion:
-  Enabled: false
-
-Layout/AlignHash:
-  EnforcedHashRocketStyle: table
-  EnforcedColonStyle: table
-
-Layout/IndentFirstArgument:
-  EnforcedStyle: consistent
-
-Layout/IndentFirstArrayElement:
-  EnforcedStyle: consistent
-
-Layout/IndentFirstHashElement:
-  EnforcedStyle: consistent
-
-Metrics/BlockLength:
-  Exclude:
-    - '*.gemspec'
-  ExcludedMethods:
-    - 'describe'
-    - 'context'
-
-Metrics/ClassLength:
-  Enabled: false
-
-Metrics/LineLength:
-  Max: 90
-
-Style/BracesAroundHashParameters:
-  EnforcedStyle: context_dependent

data/.travis.yml

@@ -1,21 +0,0 @@
-sudo: false
-language: ruby
-cache: bundler
-script: bundle exec rspec
-rvm:
-  - 2.6.3
-  - 2.5.5
-  - 2.4.6
-branches:
-  only: master
-notifications:
-  email: false
-env:
-  global:
-    - CC_TEST_REPORTER_ID=ca61b641c417ff48e8cff3c0d10e5503539bf81348b0df8daca6c74e2401d4e4
-before_script:
-  - curl -L https://codeclimate.com/downloads/test-reporter/test-reporter-latest-linux-amd64 > ./cc-test-reporter
-  - chmod +x ./cc-test-reporter
-  - ./cc-test-reporter before-build
-after_script:
-  - ./cc-test-reporter after-build --exit-code $TRAVIS_TEST_RESULT

data/.yardopts

@@ -1,8 +0,0 @@
---no-private
---protected
---markup markdown
---output-dir docs
--
-CHANGELOG.md
-LICENSE
-README.md

data/CODE_OF_CONDUCT.md

@@ -1,74 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-education, socio-economic status, nationality, personal appearance, race,
-religion, or sexual identity and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
-  advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at epistrephein@gmail.com. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 1.4, available at [https://contributor-covenant.org/version/1/4][version]
-
-[homepage]: https://contributor-covenant.org
-[version]: https://contributor-covenant.org/version/1/4/

data/CONTRIBUTING.md

@@ -1,96 +0,0 @@
-# Contributing
-
-First off, thank you for considering contributing to this project.
-
-As part of the open source community, this project thrives thanks to the help
-and the contributions of its users. There are many ways to contribute - from
-submitting bug reports and feature requests, to improving the documentation, or
-writing code which can be incorporated into the codebase.
-
-In these guidelines, you will find the most common scenarios related to
-contributing and information on how to proceed to make sure that your submission
-can be evaluated swiftly and properly.
-
-This project is intended to be a safe, welcoming space for collaboration,
-and contributors are expected to adhere to the
-[Code of Conduct](https://github.com/epistrephein/rarbg/blob/master/CODE_OF_CONDUCT.md).
-
-## Opening an issue
-
-Opening an issue on GitHub is the fastest way to get in touch with the maintainers
-of the project and start a discussion regarding a problem you're experiencing or
-a missing feature you would like to suggest.
-
-For this reason, upon opening a new issue, you'll be able to choose between
-different templates for your submission, with some pre-allocated sections to fill.
-Please try to follow the existing structure of the issue and to provide as much
-information as possible regarding your situation. This will help the maintainers
-to reproduce the bug or effectively consider the feature you'd like to see
-implemented.
-
-If you think your issue doesn't fit into any of the existing templates, or if you
-just have a question regarding the existing functionalities of the project,
-simply open a regular issue and describe the problem in the clearest way possible.
-
-## Contributing with code
-
-If you would like to contribute to the project by writing code, you can open a
-Pull Request on GitHub with your changes and ask a maintainer for a review.
-
-As an open source Ruby gem, this project uses the most common development tools
-to test, validate, and document the code.
-
-### Tools and integrations
-
-We use [RSpec](http://rspec.info/) as testing framework.  
-The test suite lives in the `spec` directory, and you can run it to test your
-changes with `rake spec`.
-
-We also use [RuboCop](https://docs.rubocop.org/en/latest/) to enforce code style.  
-The configuration file used for this project lives in `.rubocop.yml`. You can check
-the code style of your changes with `rake rubocop`.  
-Pull Requests on GitHub are automatically linted with RuboCop via [Hound](https://houndci.com/).
-
-The default Rake task, runnable using `rake`, performs code linting via Rubocop
-and then runs the RSpec tests.
-
-Documentation is written as [YARD](https://yardoc.org/) docblocks in the Ruby code.  
-This is rendered as self-hosted Web pages on [GitHub pages](https://epistrephein.github.io/rarbg/).
-Sources are stored in the repository under the `docs` folder and can be automatically
-generated and updated via `rake yard`.  
-The completeness of the documentation is then measured via
-[Inch CI](https://inch-ci.org/github/epistrephein/rarbg).
-
-Continuous integration and automated tests are run on
-[Travis CI](https://travis-ci.org/epistrephein/rarbg) and integrated with the
-GitHub Pull Request flow.
-
-Code quality and test coverage are then scored via
-[CodeClimate](https://codeclimate.com/github/epistrephein/rarbg).
-
-Finally, dependencies are kept up-to-date thanks to
-[Depfu](https://depfu.com/github/epistrephein/rarbg) integration.
-
-### Submitting a PR
-
-This project follows the [GitHub flow](https://guides.github.com/introduction/flow/)
-for Pull Request submissions.
-
-To submit a PR with your proposed changes, follow these steps:
-
-1. [Fork the repo](https://github.com/epistrephein/rarbg/fork) in your GitHub
-userspace and clone it locally
-2. Install the dependencies with bundler (`bin/setup`)
-3. Create a feature branch (`git checkout -b my-new-feature`)
-4. Add your code to the branch and then commit the changes (`git commit -am 'Add some feature'`)
-5. Run the test suite (`rake spec`) and make sure that existing and newly introduced
-tests pass. You can also run Rubocop linting with `rake rubocop`, or just use `rake`
-to run both Rubocop and RSpec tests
-6. Push to your remote branch on GitHub (`git push origin my-new-feature`)
-7. Create a [new pull request](https://github.com/epistrephein/rarbg/pulls)
-
-By submitting a patch, you agree to allow the project owners to license your work
-under the terms of the [MIT License](https://github.com/epistrephein/rarbg/blob/master/LICENSE).
-
-As for issues, when opening a new Pull Request, please fill out the template with
-all the relevant information in order to reduce the review effort of the maintainers.

data/Gemfile

@@ -1,4 +0,0 @@
-# frozen_string_literal: true
-
-source 'https://rubygems.org'
-gemspec

data/Rakefile

@@ -1,13 +0,0 @@
-# frozen_string_literal: true
-
-require 'bundler/gem_tasks'
-require 'rspec/core/rake_task'
-require 'rubocop/rake_task'
-require 'yard'
-
-RSpec::Core::RakeTask.new(:spec)
-RuboCop::RakeTask.new(:rubocop)
-YARD::Rake::YardocTask.new(:yard)
-
-# Run RuboCop and RSpec as default task.
-task default: %i[rubocop spec]

data/bin/console

@@ -1,8 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-require 'bundler/setup'
-require 'rarbg'
-require 'pry'
-
-Pry.start

data/bin/setup

@@ -1,7 +0,0 @@
-#!/usr/bin/env bash
-
-set -euo pipefail
-IFS=$'\n\t'
-set -vx
-
-bundle install

data/spec/rarbg/list_spec.rb

@@ -1,111 +0,0 @@
-# frozen_string_literal: true
-
-RSpec.describe 'RARBG::API#list' do
-  before(:all) do
-    @rarbg = RARBG::API.new
-    @token = SecureRandom.hex(5)
-  end
-
-  before(:each) do
-    stub_token(@token)
-  end
-
-  context 'when list request succeeds' do
-    before(:example) do
-      stub_list(
-        @token, {},
-        { torrent_results: [
-          {
-            filename: 'first stubbed name',
-            category: 'first stubbed category',
-            download: 'first stubbed magnet link'
-          },
-          {
-            filename: 'second stubbed name',
-            category: 'second stubbed category',
-            download: 'second stubbed magnet link'
-          }
-        ] }
-      )
-    end
-
-    it 'returns and array of hashes' do
-      expect(@rarbg.list).to all(be_an(Hash))
-    end
-
-    it 'returns hashes with filename and download link' do
-      expect(@rarbg.list).to all include('filename').and include('download')
-    end
-  end
-
-  context 'when list request returns no result' do
-    before(:example) do
-      stub_list(
-        @token, {},
-        { error: 'No results found' }
-      )
-    end
-
-    it 'returns an empty array' do
-      expect(@rarbg.list).to eq([])
-    end
-  end
-
-  context 'when list request parameters is not an hash' do
-    before(:example) do
-      stub_list(
-        @token
-      )
-    end
-
-    it 'raises an ArgumentError exception' do
-      expect { @rarbg.list('string') }.to raise_error(
-        ArgumentError, 'Expected params hash'
-      )
-    end
-  end
-
-  context 'when list request has invalid parameters' do
-    before(:example) do
-      stub_list(
-        @token,
-        { min_seeders: 'string' },
-        { error: 'Invalid value for min_seeders' }
-      )
-    end
-
-    it 'raises a RARBG::APIError exception' do
-      expect { @rarbg.list(min_seeders: 'string') }.to raise_error(
-        RARBG::APIError, 'Invalid value for min_seeders'
-      )
-    end
-  end
-
-  context 'when list request fails' do
-    before(:example) do
-      stub_error(500, 'Internal Server Error')
-    end
-
-    it 'raises a RARBG::APIError exception' do
-      expect { @rarbg.list }.to raise_error(
-        RARBG::APIError, 'Internal Server Error (500)'
-      )
-    end
-  end
-
-  context 'when called from top level namespace' do
-    let(:rarbg_module) { RARBG.clone }
-
-    before(:example) do
-      stub_list(
-        @token
-      )
-    end
-
-    it 'instantiates an API object' do
-      expect { rarbg_module.list }
-        .to change { rarbg_module.instance_variable_get(:@rarbg).class }
-        .to(RARBG::API)
-    end
-  end
-end