mercadopago-sdk 1.2.0 → 2.0.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 40a42ea53dd82c6c9932c0c603b23920bf03c89d6823a3779a99f778b99d361d
-  data.tar.gz: 1c8bea06955578aff4de9afcd4ae03f4a375ae3f1a2bda31014c301148997740
+  metadata.gz: b8e6135cb3e0d5f8f0c998dfb10e9df4cf73277c8668f4828f8e5546278e6d2b
+  data.tar.gz: 1146f18fff0281cce92e9da15277a526bd3f739fcd456967aa2a3c8de6827bd6
 SHA512:
-  metadata.gz: f1da53205f33babf2452c51a242b2cd2e8b87d069cfe8b61fc634ec04a53c46f5cbee8e0c88cf86fb7b6fe3dcc1e596e028b2255bd6a1ee738b551ee09f43d16
-  data.tar.gz: eca076db10b08db2074d4703dbd69bd645855e06a23847f4ef05f8625276f4188eef81ed4c8175f9cb28074a40e895a10b051eb8ce92559964e39428564c0968
+  metadata.gz: 0c6420857efa67afe2a7524e0e23a996d7d5805550921321eff0eaac1cf07770b82069ee0b776e642ad3bdba6124c2d44874530832a152b02c8adc9c3d593164
+  data.tar.gz: 1507f8d854b70dd1ad8d9be129b245824c6c04f5caf16b9e6b03c96225f8b7d966380c1f3cdfdb1c874b65fbefacc0bfdc9d883012a6c22f10e540d57b0c922b

data/.editorconfig

@@ -0,0 +1,10 @@
+# see http://editorconfig.org/
+
+root = true
+
+[*]
+indent_style = space
+indent_size = 2
+end_of_line = lf
+charset = utf-8
+insert_final_newline = true

data/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,28 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+
+- Test case to reproduce the bug.  Try to reproduce in the latest version.
+- Code sample that fails
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Environment (please complete the following information):**
+
+- OS: [e.g. Linux/Mac/Windows]
+- Ruby version: [e.g. 2.3]
+- SDK version: [e.g. 2.0.0]
+
+**Additional context**
+Add any other context about the problem here. [e.g. Links to previous bugs].

data/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,19 @@
+---
+name: Feature request
+about: Suggest completely new features or minor improvements to existing functionality
+title: ''
+labels: enhancement, proposed
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

data/.github/workflows/ruby.yml

@@ -0,0 +1,35 @@
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+# This workflow will download a prebuilt Ruby version, install dependencies and run tests with Rake
+# For more information see: https://github.com/marketplace/actions/setup-ruby-jruby-and-truffleruby
+
+name: Ruby
+
+on:
+  push:
+    branches: [ master ]
+  pull_request:
+    branches: [ master ]
+
+jobs:
+  test:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v2
+    - name: Set up Ruby
+    # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby,
+    # change this to (see https://github.com/ruby/setup-ruby#versioning):
+    # uses: ruby/setup-ruby@v1
+      uses: ruby/setup-ruby@21351ecc0a7c196081abca5dc55b08f085efe09a
+      with:
+        ruby-version: 2.6
+    - name: Install dependencies
+      run: bundle install
+    - name: Rubocop
+      run: rubocop lib
+    - name: Run tests
+      run: bundle exec rake

data/.rubocop.yml

@@ -0,0 +1 @@
+inherit_from: .rubocop_todo.yml

data/.rubocop_todo.yml

@@ -0,0 +1,104 @@
+# This configuration was generated by
+# `rubocop --auto-gen-config`
+# on 2021-01-06 19:35:39 UTC using RuboCop version 1.7.0.
+# The point is for the user to remove these configuration records
+# one by one as the offenses are removed from the code base.
+# Note that changes in the inspected code, or installation of new
+# versions of RuboCop, may require this file to be generated again.
+
+# Offense count: 1
+# Configuration parameters: Include.
+# Include: **/*.gemspec
+Gemspec/RequiredRubyVersion:
+  Exclude:
+    - 'mercadopago.gemspec'
+
+# Offense count: 8
+Lint/SelfAssignment:
+  Exclude:
+    - 'lib/mercadopago/core/mp_base.rb'
+
+# Offense count: 1
+# Cop supports --auto-correct.
+# Configuration parameters: AllowUnusedKeywordArguments, IgnoreEmptyMethods, IgnoreNotImplementedMethods.
+Lint/UnusedMethodArgument:
+  Exclude:
+    - 'lib/mercadopago/resources/disbursement_refund.rb'
+
+# Offense count: 36
+Lint/UselessAssignment:
+  Exclude:
+    - 'examples/instant-payment-notifications/receive-ipn.rb'
+    - 'lib/mercadopago/core/mp_base.rb'
+    - 'lib/mercadopago/http/http_client.rb'
+    - 'lib/mercadopago/resources/advanced_payment.rb'
+    - 'lib/mercadopago/resources/disbursement_refund.rb'
+    - 'tests/test_card.rb'
+    - 'tests/test_card_token.rb'
+
+# Offense count: 2
+# Configuration parameters: IgnoredMethods, CountRepeatedAttributes.
+Metrics/AbcSize:
+  Max: 25
+
+# Offense count: 15
+# Configuration parameters: CountComments, CountAsOne, ExcludedMethods, IgnoredMethods.
+Metrics/MethodLength:
+  Max: 69
+
+# Offense count: 3
+# Configuration parameters: CountKeywordArgs, MaxOptionalParameters.
+Metrics/ParameterLists:
+  Max: 7
+
+# Offense count: 1
+Naming/AccessorMethodName:
+  Exclude:
+    - 'lib/mercadopago/config/request_options.rb'
+
+# Offense count: 6
+# Configuration parameters: ExpectMatchingDefinition, CheckDefinitionPathHierarchy, Regex, IgnoreExecutableScripts, AllowedAcronyms.
+# AllowedAcronyms: CLI, DSL, ACL, API, ASCII, CPU, CSS, DNS, EOF, GUID, HTML, HTTP, HTTPS, ID, IP, JSON, LHS, QPS, RAM, RHS, RPC, SLA, SMTP, SQL, SSH, TCP, TLS, TTL, UDP, UI, UID, UUID, URI, URL, UTF8, VM, XML, XMPP, XSRF, XSS
+Naming/FileName:
+  Exclude:
+    - 'examples/instant-payment-notifications/receive-ipn.rb'
+    - 'examples/payment-search/search-approved-payments.rb'
+    - 'examples/payment-search/search-creditcard-payments.rb'
+    - 'examples/payment-search/search-funded-payments-by-name.rb'
+    - 'examples/payment-search/search-payments-from-email-and-date.rb'
+    - 'examples/payment-search/search-payments.rb'
+
+# Offense count: 23
+# Configuration parameters: EnforcedStyle.
+# SupportedStyles: snake_case, camelCase
+Naming/VariableName:
+  Exclude:
+    - 'examples/checkout-buttons/basic_preference/button.rb'
+    - 'examples/payment-search/search-approved-payments.rb'
+    - 'examples/payment-search/search-creditcard-payments.rb'
+    - 'examples/payment-search/search-funded-payments-by-name.rb'
+    - 'examples/payment-search/search-payments-from-email-and-date.rb'
+    - 'examples/payment-search/search-payments.rb'
+    - 'examples/preapproval-payments/button.rb'
+    - 'lib/mercadopago/config/config.rb'
+
+# Offense count: 7
+Style/ClassVars:
+  Exclude:
+    - 'lib/mercadopago/config/config.rb'
+
+# Offense count: 32
+Style/Documentation:
+  Enabled: false
+
+# Offense count: 2
+Style/IdenticalConditionalBranches:
+  Exclude:
+    - 'examples/instant-payment-notifications/receive-ipn.rb'
+
+# Offense count: 12
+# Cop supports --auto-correct.
+# Configuration parameters: AutoCorrect, AllowHeredoc, AllowURI, URISchemes, IgnoreCopDirectives, IgnoredPatterns.
+# URISchemes: http, https
+Layout/LineLength:
+  Max: 151

data/.ruby-version

@@ -0,0 +1 @@
+2.3.0

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# 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,
+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 [developers.mercadopago.com](https://www.mercadopago.com/developers). 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/CODING_GUIDELINES.md

@@ -0,0 +1,70 @@
+# Coding Guidelines
+
+The Mercado Pago Ruby SDK is a collaborative effort from the start. The SDK team thinks that contributions from different developer will enrich it's feature set and make it more relevant to the community.
+
+However; absorbing all contributions as-is, while expedient, might lead to difficulties in maintenance of the codebase is left unchecked. Collaborative codebases often establish guidelines for contributors to ensure code remains maintainable over time. The effort to maintain the SDK is no different in this regard so a bit of guidance is in order.
+
+The purpose of this guide is to set a baseline for contributions. These guidelines are not intended to limit the tools at your disposal nor to rewire the way you think but rather to encourage good neighbor behavior.
+
+## Language Guidelines
+
+We use **english** language. This is to be consistent everywhere, and to be considerate with developers that do not speak our native language.
+
+Therefore: source code, comments, documentation, commit messages, review comments, and any other kind of contribution *MUST* use english language.
+
+Typos are unavoidable, but try to reduce them by using a spellchecker. Most IDEs can be configured to run one automatically.
+
+## Code Guidelines
+
+* Set your IDE to follow the [`.editorconfig`](https://editorconfig.org/) in each repository.
+* Follow the [RuboCop Ruby Style Guide](https://github.com/rubocop/ruby-style-guide).
+
+Generally speaking, be conscious when contributing and try following the same style that the code in the SDK already has. If you have any doubts, just ask us!
+
+This rules will be enforced automatically when making a pull requests, and checks will fail if you do not follow them, resulting in your contribution being automatically rejected until fixed.
+
+## Comment Guidelines
+
+Comments in code are a hard thing to write, not because the words are difficult to produce but because it is hard to make relevant comments. Too much of it and people do not read comments (and it obfuscates code reading) and too little of it gives you no recourse but to read large portions of codebase to get insight as to what a feature/codeblock is doing. Both situations are undesirable and efforts should be made at all time to have a please comment reading experience
+
+As a general rule you would have to comment on decisions you made while coding that are not part of any specification.
+
+In particular you should always comment any decision that:
+
+* Departs from common wisdom or convention (The **why's** are necessary).
+* Takes a significant amount of time to produce. A good rule of thumb here is that if you spent more than 1 hour thinking on how to produce a fragment of code that took 2 minutes of wrist time to write you should document your thinking to aid reader and allow for validation.
+* Need to preserve properties of the implementation. This is the case of performance sensitive portions of the codebase, goroutines synchronization, implementations of security primitives, congestion control algorithms, etc.
+
+As a general rule of what not to comment you should avoid:
+
+* Commenting on structure of programs that is already part of a convention, specified or otherwise.
+* Having pedantic explanations of behavior that can be found by immediate examination of the surrounding code artifacts.
+* Commenting on behavior you cannot attest.
+
+### Branching Guidelines
+
+Currently `master` is our only long term branch, below a few suggestions of short term branches naming:
+
+* `hotfix/something-needs-fix`: Small routine patches in code to features already there.
+* `feature/something-new`: A new feature or a change in a existent feature. Beware of breaking changes that would require a major version bump.
+* `doc/improves-documentation-for-this-feature`: If you add or change documentation with no impact to the source code.
+
+### Git Guidelines
+
+All commits **SHOULD** follow the [seven rules of a great Git commit message](https://chris.beams.io/posts/git-commit):
+
+1. Separate subject from body with a blank line.
+2. Limit the subject line to 72 characters.
+3. Capitalize the subject line.
+4. Do not end the subject line with a period.
+5. Use the imperative mood in the subject line.
+6. Wrap the body at 72 characters.
+7. Use the body to explain what and why vs. how.
+
+Commits such as "fix tests", "now it's working" and many other common messages we find usually in code **WON'T** be accepted.
+
+Ideally we would like to enforce these rules, but we are realistic and understand that it might be a big change for some people. So unless deviating heavily from what was stated we might accept your commits even if not following these rules perfectly.
+
+Please avoid taking to much time to deliver code, and always [rebase](https://git-scm.com/docs/git-rebase) your code to avoid reverse merge commits.
+
+When reviewing, check if the PR adheres to [RuboCop Ruby Style Guide](https://github.com/rubocop/ruby-style-guide).

data/CONTRIBUTING.md

@@ -0,0 +1,57 @@
+# Contributing to the Mercado Pago Ruby SDK
+
+Thank you for your interest in contributing to the Mercado Pago Ruby SDK!
+
+## How to contribute
+
+In order to contribute to the Mercado Pago Ruby SDK effectively we provide guidelines to address common case for contributions. Presently we have guides for the following type of changes.
+
+* Request For Change (RFC) / Feature Request: These are suggestions / requests for features the SDK currently does not have. The SDK team evaluates these requests for adequacy / relevance / capacity and overall architectural consistency.
+* Bug Reports: These are reports of non compliant behavior with the SDK specification and other blatantly wrong behavior of the Mercado Pago Ruby SDK.
+
+In addition to contributing in the form of Bug Reports and RFCs it is also possible to contribute directly in code with a Pull Request (PR). In the case of a Pull Request you should also indicate the nature of the Pull Request (Feature/Bug/etc.) to help the team asses the Pull Request. If you are enthusiastic about a particular Feature being added or a bug being fixed, a PR is often the quickest way to promote your change as the team does not have to allocate as much resources to process the contribution.
+
+In the case of PRs it is often best to consult with the SDK team before embarking on a PR, specially if it's a beefy one. Spending time on a PR that might later be rejected because major discrepancies with vision or competing contributions is an uncomfortable outcome for all involved people. Remember the SDK team with privilege overall consistency and progress over any one particular contribution.
+
+## Coding Guidance
+
+All contributions *MUST* follow the [Coding Guidelines](CODING_GUIDELINES.md). Contributions that fail to follow this guidelines will be disregarded and told to make the required modifications to do so.
+
+## Request For Change / Feature Request
+
+Generally speaking an RFC is needed when you want to add a new feature or change an existing one in an incompatible way that might result in a major version bump to the toolkit.
+
+Though it seems a little bureaucratic, the process is in place in order to avoid frustration of a potential contributor by making the discussions take place before any code is written. Once the design and direction is fully agreed then the contributor can work peacefully knowing that their change will be committed.
+
+As of this moment all you need to do is create an issue and use the [Feature Request Template](.github/ISSUE_TEMPLATE/feature_request.md).
+
+Please prepend your issue title with `[RFC]` so that's easier to filter.
+
+## Bug Reports
+
+Bugs are a reality in software. We can't fix what we don't know about, so please report liberally. If you're not sure if something is a bug or not, feel free to file it anyway.
+
+Before reporting a bug, please search existing issues and pull requests, as it's possible that someone else has already reported your error. In the off case that you find your issue as fixed/closed, please add a reference to it on your new one.
+
+Your issue should contain a title and a clear description of the issue. You should also include as much relevant information as possible and a code sample that demonstrates the issue. The goal of a bug report is to make it easy for yourself - and others - to replicate the bug and develop a fix.
+
+Opening an issue is as easy as following [this link](https://github.com/mercadopago/sdk-dotnet/issues/new) and filling out the given template.
+
+Bug reports may also be sent in the form of a [pull request](#pull-request) containing a failing test.
+
+## Pull Request
+
+First and foremost: Source code, documentation, commit messages, review comments, and any other kind of contribution must *MUST* follow the [Coding Guidelines](CODING_GUIDELINES.md).
+
+We use the "fork and pull" model [described here](https://help.github.com/articles/about-collaborative-development-models/), where contributors push changes to their personal fork and create pull requests to bring those changes into the source repository.
+
+Your basic steps to get going:
+
+* Fork the corresponding toolkit repository and create a branch from master for the issue you are working on.
+* Commit as you go following our git conventions.
+* Include tests that cover all non-trivial code. The existing tests should provide a template on how to test the toolkit correctly.
+* Make sure all test passes.
+* All code changes are expected to comply with the formatting style.
+* Push your commits to GitHub and create a pull request against the corresponding toolkit component master branch.
+
+If taking to much time to deliver code, **always** [rebase](https://git-scm.com/docs/git-rebase) towards `master` before asking for a review, and avoid reverse merge commits.

data/Gemfile

@@ -1,3 +1,11 @@
+# frozen_string_literal: true
+
 source 'https://rubygems.org'
 
+group :development, :test do
+  gem 'rake'
+  gem 'minitest'
+  gem 'rubocop', require: false
+end
+
 gemspec

data/Gemfile.lock

@@ -1,26 +1,65 @@
 PATH
   remote: .
   specs:
-    mercadopago-sdk (0.3.5)
-      json
+    mercadopago-sdk (2.0.3)
+      json (~> 2.5)
+      rest-client (~> 2.1)
 
 GEM
   remote: https://rubygems.org/
   specs:
-    coderay (1.0.9)
-    json (1.8.3)
-    method_source (0.8.1)
-    pry (0.9.12)
-      coderay (~> 1.0.5)
-      method_source (~> 0.8)
-      slop (~> 3.4)
-    rake (10.0.3)
-    slop (3.4.4)
+    ast (2.4.2)
+    coderay (1.1.3)
+    domain_name (0.5.20190701)
+      unf (>= 0.0.5, < 1.0.0)
+    http-accept (1.7.0)
+    http-cookie (1.0.4)
+      domain_name (~> 0.5)
+    jaro_winkler (1.5.4)
+    json (2.6.1)
+    method_source (1.0.0)
+    mime-types (3.4.1)
+      mime-types-data (~> 3.2015)
+    mime-types-data (3.2021.1115)
+    minitest (5.14.4)
+    netrc (0.11.0)
+    parallel (1.19.2)
+    parser (3.0.1.0)
+      ast (~> 2.4.1)
+    pry (0.14.1)
+      coderay (~> 1.1)
+      method_source (~> 1.0)
+    rainbow (3.0.0)
+    rake (13.0.3)
+    rest-client (2.1.0)
+      http-accept (>= 1.7.0, < 2.0)
+      http-cookie (>= 1.0.2, < 2.0)
+      mime-types (>= 1.16, < 4.0)
+      netrc (~> 0.8)
+    rexml (3.2.5)
+    rubocop (0.81.0)
+      jaro_winkler (~> 1.5.1)
+      parallel (~> 1.10)
+      parser (>= 2.7.0.1)
+      rainbow (>= 2.2.2, < 4.0)
+      rexml
+      ruby-progressbar (~> 1.7)
+      unicode-display_width (>= 1.4.0, < 2.0)
+    ruby-progressbar (1.11.0)
+    unf (0.1.4)
+      unf_ext
+    unf_ext (0.0.8)
+    unicode-display_width (1.7.0)
 
 PLATFORMS
   ruby
 
 DEPENDENCIES
   mercadopago-sdk!
-  pry
+  minitest
+  pry (~> 0.14)
   rake
+  rubocop
+
+BUNDLED WITH
+   2.2.22

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2021 Mercado Pago
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.