conekta 2.6.0 → 6.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 31713f94324383d6c460c26a4d948ab1684c86286a4181d94a1bcf448b906ce9
-  data.tar.gz: 8ffa91279cf24f52d6367903a469763bd77458cfaed1cb22728adc655ac296e3
+  metadata.gz: 8475970315cc9577bcca3710ec319404e61407ae0b1b8348504c9e778c7762a8
+  data.tar.gz: 144cc479f358ab1e6d3be7fc2281806580851ab74b77b63858a4bccb34eedc6d
 SHA512:
-  metadata.gz: c90d1fa11514c232911156531a8794571ecc0800ef8276f8071df12a5e8b428458d7c8bfb8c808818d6ca56f2d73ca38f1224e9d8c1ac121d55b1f055c81e61d
-  data.tar.gz: 03ba2731ac8b69c7967baff8cd56df145ba62b34c021c12e68b8a91b5e5a79b5b3f9f15785d2a6728a7da6f87f61b9ac7f693a5c7a9381354e5cd79d214a1bfe
+  metadata.gz: b94fab0b74a1c5838b66db6906267760cb138dffcfa45188a0526a122fe97551f4f6c339b7ec8d6080f98946124a298f08eff656418a0b301718b2bde5fcfe68
+  data.tar.gz: 59cfb638311085debcf81edc79f32f7336836749818a93b423d8cbefec2240964f14de5847af4a8a0c7529fb7d44161edffa811ab68ed2b63ab9239bb3a871ea

data/AUTHORS.md

@@ -0,0 +1,28 @@
+title: Authors
+
+Primary Authors
+===============
+
+* __[Franklin Carrero](https://github.com/fcarrero)__
+
+    @fcarrero is the current maintainer of the code and has written much of the
+    current code base, including a complete refactor of the core for version 2.0.
+    He started out by authoring many of the available extensions and later was
+    asked to join Yuri, where he began fixing numerous bugs, adding
+    documentation and making general improvements to the existing code base.
+
+* __[Jorge Alberto Alonso](https://github.com/jalonsoDevConekta)__
+
+    @jalonsoDevConekta is the current maintainer of the code and has written much of the
+    current code base, including a complete refactor of the core for version 2.0.
+    He started out by authoring many of the available extensions and later was
+    asked to join Yuri, where he began fixing numerous bugs, adding
+    documentation and making general improvements to the existing code base.
+    
+* __[Ezequiel Rozen](https://github.com/ezerozen)__
+
+    @ezerozen is the current maintainer of the code and has written much of the
+    current code base, including a complete refactor of the core for version 2.0.
+    He started out by authoring many of the available extensions and later was
+    asked to join Yuri, where he began fixing numerous bugs, adding
+    documentation and making general improvements to the existing code base.

data/CHANGELOG.md

@@ -1,3 +1,11 @@
+## [6.0.0](https://github.com/conekta/conekta-ruby/releases/tag/6.0.0) - 2023-08-01
+## What's Changed
+* Fix i18n dependency load error by @juanolivas in https://github.com/conekta/conekta-ruby/pull/108
+* Removing ConektaList.total logic in favor of has_more by @leofischer in https://github.com/conekta/conekta-ruby/pull/105
+* Update README by @fernandosaenzconekta in https://github.com/conekta/conekta-ruby/pull/109
+* Readme changes by @fernandosaenzconekta in https://github.com/conekta/conekta-ruby/pull/110
+* Fix Specs by @nicocedron in https://github.com/conekta/conekta-ruby/pull/111
+* openapi by @fcarrero in https://github.com/conekta/conekta-ruby/pull/114
 ## [2.6.0](https://github.com/conekta/conekta-ruby/releases/tag/2.5.0) - 2020-06-08
 ### Deprecate List Total attribute
 - Remove total attribute logic for lists as it is deprecated and will be removed.

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,77 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to make participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, 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 within all project spaces, and it also applies when
+an individual is representing the project or its community in public spaces.
+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 engineering@conekta.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://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq
+

data/CONTRIBUTING.md

@@ -0,0 +1,19 @@
+# Contribution guidelines
+
+## How to contribute step-by-step
+
+1. Fork the `conekta/#$repo repository.
+2. Create a new branch from `main` in your fork. This makes it easier for you to keep track of your changes.
+3. Make the desired changes to the code.
+    * If you are adding new functionality or fixing a bug, we recommend you add unit tests that cover it.
+4. Push the changes to your fork.
+5. Create a pull request to the `conekta/#$repo` repository.
+6. In your pull request, please describe in detail:
+    * What problem you’re solving
+    * Your approach to fixing the problem
+    * Any tests you wrote
+7. Check Allow edits from maintainers.
+8. Create the pull request.
+9. Ensure that all checks have passed.
+
+After you create your pull request, one of the code owners will review your code. We aim to review your request within 2-3 business days.

data/Gemfile

@@ -1,13 +1,9 @@
 source 'https://rubygems.org'
-gem 'sys-uname'
-gem 'rspec'
-gem 'faraday'
-gem 'json'
-gem 'i18n'
+
+gemspec
 
 group :development, :test do
-  gem 'byebug'
+  gem 'rake', '~> 13.0.1'
+  gem 'pry-byebug'
+  gem 'rubocop', '~> 0.66.0'
 end
-
-# Specify your gem's dependencies in conekta.gemspec
-gemspec

data/{LICENSE.txt → LICENSE}

@@ -19,4 +19,4 @@ 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.
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/Makefile

@@ -0,0 +1,2 @@
+ci-test:
+	bundle exec rspec