poodle-ruby 1.0.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: e75538a170e922587d7cd3f4eaa08dc36b2898538e805c6c26cdc8337fc96388
+  data.tar.gz: 101dbf4fb3066bbda66d618fc65c3684e93481148fb6e4cb6e08a8734c6bf219
+SHA512:
+  metadata.gz: 96d53647e88eeb5288a7584fb085e7c32badfe379bc78747b807123f7dd651b1b046d3618a783d238c892914c5d0f9d689c9c3d6d1a8ba5b43eb13dd1e2d7e76
+  data.tar.gz: 6fbf47f1ff168074eb3c433ff9cf13cbc4e2655e01d6eb3eb90e4f42e4869f056ae7ac031549768eab15c5949c8b467db3798b68661e7a6233ff09f1b6a92cb8

data/.rspec

@@ -0,0 +1 @@
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,65 @@
+AllCops:
+  SuggestExtensions: false
+  TargetRubyVersion: 3.0
+  NewCops: enable
+  Exclude:
+    - "vendor/**/*"
+    - "bin/**/*"
+    - "spec/fixtures/**/*"
+
+# Style preferences
+Style/StringLiterals:
+  Enabled: true
+  EnforcedStyle: double_quotes
+
+Style/Documentation:
+  Enabled: false
+
+Style/FrozenStringLiteralComment:
+  Enabled: true
+
+# Layout preferences
+Layout/LineLength:
+  Max: 120
+  Exclude:
+    - "spec/**/*"
+
+# Metrics
+Metrics/BlockLength:
+  Exclude:
+    - "spec/**/*"
+    - "poodle-ruby.gemspec"
+    - "lib/poodle/rails/tasks.rake"
+    - "examples/**/*"
+
+Metrics/MethodLength:
+  Max: 20
+  Exclude:
+    - "spec/**/*"
+    - "examples/**/*"
+
+Metrics/ClassLength:
+  Max: 170
+
+# Naming
+Naming/FileName:
+  Exclude:
+    - "lib/poodle-ruby.rb"
+
+# Security
+Security/YAMLLoad:
+  Enabled: true
+
+Metrics/AbcSize:
+  Max: 20
+  Exclude:
+    - "examples/**/*"
+
+Metrics/CyclomaticComplexity:
+  Max: 8
+  Exclude:
+    - "examples/**/*"
+
+Metrics/PerceivedComplexity:
+  Exclude:
+    - "examples/**/*"

data/.yardopts

@@ -0,0 +1,12 @@
+--markup markdown
+--markup-provider kramdown
+--output-dir doc
+--protected
+--private
+--title "Poodle Ruby SDK Documentation"
+--readme README.md
+--files CHANGELOG.md,LICENSE
+lib/**/*.rb
+-
+README.md
+CHANGELOG.md

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,78 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible 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.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Project maintainers are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+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, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our 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.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the project team at support@usepoodle.com. All complaints will be reviewed and investigated promptly and fairly.
+
+All project maintainers are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Project maintainers will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from project maintainers, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq.
+

data/CONTRIBUTING.md

@@ -0,0 +1,151 @@
+# Contributing to Poodle Ruby SDK
+
+Thank you for your interest in contributing to the Poodle Ruby SDK! We welcome contributions from the community.
+
+## Development Setup
+
+### Requirements
+
+- Ruby 3.0 or higher
+- Bundler
+- Git
+
+### Setup
+
+1. Fork the repository
+2. Clone your fork:
+
+   ```bash
+   git clone https://github.com/yourusername/poodle-ruby.git
+   cd poodle-ruby
+   ```
+
+3. Install dependencies:
+   ```bash
+   bundle install
+   ```
+
+## Development Workflow
+
+### Running Tests
+
+```bash
+# Run all tests
+bundle exec rspec
+
+# Run specific test file
+bundle exec rspec spec/poodle/client_spec.rb
+
+# Run tests with coverage
+bundle exec rspec
+# Coverage report will be generated in coverage/index.html
+```
+
+### Code Quality
+
+```bash
+# Check code style
+bundle exec rubocop
+
+# Fix code style issues automatically
+bundle exec rubocop -a
+
+# Generate documentation
+bundle exec yard doc
+
+# View documentation
+bundle exec yard server
+```
+
+### Making Changes
+
+1. Create a feature branch:
+
+   ```bash
+   git checkout -b feature/your-feature-name
+   ```
+
+2. Make your changes
+3. Write or update tests
+4. Ensure all tests pass and code style is correct
+5. Commit your changes with a descriptive message
+6. Push to your fork
+7. Create a pull request
+
+## Code Standards
+
+### Ruby Standards
+
+- Follow the Ruby Style Guide
+- Use RuboCop for code style enforcement (configuration in `.rubocop.yml`)
+- Maintain Ruby 3.0+ compatibility
+- Use frozen string literals (`# frozen_string_literal: true`)
+- Write comprehensive YARD documentation
+
+### Testing Standards
+
+- Write RSpec tests for all new functionality
+- Maintain or improve test coverage
+- Use descriptive test descriptions
+- Test both success and failure scenarios
+- Use VCR for HTTP interaction testing when appropriate
+
+### Documentation Standards
+
+- Document all public methods with YARD
+- Update README.md if adding new features
+- Include code examples in documentation
+- Keep examples in the `examples/` directory up to date
+
+## Pull Request Process
+
+1. Ensure your code follows the existing style and conventions
+2. Run the full test suite and ensure all tests pass
+3. Run RuboCop and fix any style issues
+4. Update documentation as needed
+5. Write a clear PR description explaining your changes
+6. Link any relevant issues
+
+## We Use [Github Flow](https://docs.github.com/en/get-started/using-github/github-flow)
+
+Pull requests are the best way to propose changes to the codebase. We actively welcome your pull requests:
+
+1. Fork the repo and create your branch from `main`.
+2. If you've added code that should be tested, add tests.
+3. If you've changed APIs, update the documentation.
+4. Ensure the test suite passes.
+5. Make sure your code follows RuboCop guidelines.
+6. Issue that pull request!
+
+## Any contributions you make will be under the MIT Software License
+
+In short, when you submit code changes, your submissions are understood to be under the same [MIT License](http://choosealicense.com/licenses/mit/) that covers the project. Feel free to contact the maintainers if that's a concern.
+
+## Report bugs using GitHub's [issue tracker](https://github.com/usepoodle/poodle-ruby/issues)
+
+We use GitHub issues to track public bugs. Report a bug by [opening a new issue](https://github.com/usepoodle/poodle-ruby/issues/new); it's that easy!
+
+## Write bug reports with detail, background, and sample code
+
+**Great Bug Reports** tend to have:
+
+- A quick summary and/or background
+- Steps to reproduce
+  - Be specific!
+  - Give sample code if you can.
+- What you expected would happen
+- What actually happens
+- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
+
+## Use a Consistent Coding Style
+
+- Follow the RuboCop configuration in `.rubocop.yml`
+- Use double quotes for strings
+- 2 spaces for indentation
+- Maximum line length of 120 characters
+- Write meaningful commit messages
+- Use descriptive variable and method names
+
+## License
+
+By contributing, you agree that your contributions will be licensed under its MIT License.

data/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Poodle
+
+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.