geminize 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: a9b29587f96d7535a7db3ad010684fd9fa7e7a765d83d71a1cd645bdf323af69
+  data.tar.gz: 90adc36f2b5acbdb6e45904ebbd7847d1a895a614d4aee6ace5af028d8812045
+SHA512:
+  metadata.gz: 0b303213d67decca74c5f14c1a94625275febe0fc50d1ca24dc5a12fd65cd148077ef50e6ca27f1e720e05e88101f76047088db2707b71f2318036b7351335f9
+  data.tar.gz: 981b130896dd8a0f8824602d0adb51fe60b8cfcab9124b3e7322795b6cfc9c8140031a6ca144e042c478182e78d2f3f00a9e35daa3c763a2f6d794171f4773ed

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.standard.yml

@@ -0,0 +1,3 @@
+# For available configuration options, see:
+#   https://github.com/standardrb/standard
+ruby_version: 3.1

data/.yardopts

@@ -0,0 +1,14 @@
+--markup markdown
+--markup-provider redcarpet
+--title "Geminize Documentation"
+--protected
+--no-private
+--exclude /spec/
+--exclude /bin/
+--hide-void-return
+--embed-mixins
+--readme README.md
+lib/**/*.rb
+-
+LICENSE.txt
+CHANGELOG.md

data/CHANGELOG.md

@@ -0,0 +1,24 @@
+## [Unreleased]
+
+### Added
+
+- Rails integration for easy use in Rails applications
+  - Rails engine for seamless integration
+  - Generator for creating configuration initializers
+  - Controller concerns for Gemini operations
+  - View helpers for rendering conversations and chat interfaces
+  - Comprehensive documentation and examples
+- Multimodal support for sending mixed content including text and images to the Gemini API
+- New `generate_text_multimodal` method at module level for simplified multimodal requests
+- Methods for adding images to content requests from files, URLs, or raw bytes
+- Support for common image formats (JPEG, PNG, GIF, WEBP) with proper MIME type detection
+- Comprehensive validation for image formats, sizes, and content
+- New example file demonstrating multimodal usage
+- Extended embedding support with all Google AI task types:
+  - Added `TASK_TYPE_UNSPECIFIED`, `QUESTION_ANSWERING`, `FACT_VERIFICATION`, and `CODE_RETRIEVAL_QUERY` task types
+  - Updated examples and documentation to demonstrate all task types
+  - Added tests for all new task types
+
+## [0.1.0] - 2025-04-21
+
+- Initial release

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# 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, caste, color, 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 sexual attention or advances of
+  any kind
+* 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
+
+Community leaders 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.
+
+Community leaders 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 email 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 community leaders responsible for enforcement at
+[INSERT CONTACT METHOD].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders 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 community leaders, 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][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

data/CONTRIBUTING.md

@@ -0,0 +1,109 @@
+# Contributing to Geminize
+
+First of all, thank you for considering contributing to Geminize! It's people like you that make Geminize better for everyone.
+
+## Code of Conduct
+
+This project and everyone participating in it is governed by the [Geminize Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [nhatlongnguyen1992@gmail.com](mailto:nhatlongnguyen1992@gmail.com).
+
+## How Can I Contribute?
+
+### Reporting Bugs
+
+This section guides you through submitting a bug report. Following these guidelines helps maintainers understand your report, reproduce the behavior, and fix the issue.
+
+- **Use a clear and descriptive title** for the issue to identify the problem.
+- **Describe the exact steps which reproduce the problem** in as many details as possible.
+- **Provide specific examples to demonstrate the steps** such as code snippets or links to your implementation.
+- **Describe the behavior you observed after following the steps** and point out what exactly is the problem with that behavior.
+- **Explain which behavior you expected to see instead and why.**
+- **Include screenshots or animated GIFs** which show you following the described steps and clearly demonstrate the problem.
+- **If the problem is related to performance or memory usage**, include a profiling report if possible.
+- **If the problem wasn't triggered by a specific action**, describe what you were doing before the problem happened.
+
+### Suggesting Enhancements
+
+This section guides you through submitting an enhancement suggestion, including completely new features and minor improvements to existing functionality.
+
+- **Use a clear and descriptive title** for the issue to identify the suggestion.
+- **Provide a step-by-step description of the suggested enhancement** in as many details as possible.
+- **Provide specific examples to demonstrate the steps** if applicable.
+- **Describe the current behavior** and **explain which behavior you expected to see instead** and why.
+- **Explain why this enhancement would be useful** to most Geminize users.
+
+### Pull Requests
+
+- Fill in the required template
+- Do not include issue numbers in the PR title
+- Include screenshots and animated GIFs in your pull request whenever possible
+- Follow the Ruby style guide (see below)
+- Include tests for new functionality
+- Document new code
+
+## Development Environment Setup
+
+1. Fork the repo
+2. Clone your fork: `git clone https://github.com/your-username/geminize.git`
+3. Change to the project directory: `cd geminize`
+4. Install dependencies: `bundle install`
+5. Run the tests: `bundle exec rake spec`
+
+## Ruby Style Guide
+
+We use [StandardRB](https://github.com/standardrb/standard) for code styling. Before submitting a PR, please run:
+
+```bash
+bundle exec standardrb --fix
+```
+
+## Testing
+
+We use RSpec for testing. Please ensure all your code is tested:
+
+```bash
+bundle exec rspec
+```
+
+For comprehensive testing with VCR cassettes (which record API calls), ensure to set up a valid `GEMINI_API_KEY` in your environment or in a `.env` file.
+
+## Documentation
+
+We use YARD for documentation. Please document all public methods and classes using YARD syntax:
+
+```ruby
+# This method does something useful
+#
+# @param name [String] The name to use
+# @param options [Hash] Additional options
+# @option options [Boolean] :recursive Whether to recursively process
+# @return [Array<String>] A list of processed results
+def some_method(name, options = {})
+  # ...
+end
+```
+
+## Versioning
+
+We follow [Semantic Versioning](https://semver.org/). In short:
+
+- MAJOR version for incompatible API changes
+- MINOR version for added functionality in a backwards-compatible manner
+- PATCH version for backwards-compatible bug fixes
+
+## Releasing
+
+Only maintainers can create releases. The process is:
+
+1. Update version in `lib/geminize/version.rb`
+2. Update `CHANGELOG.md` with changes since last release
+3. Commit: `git commit -am "Prepare for release vX.Y.Z"`
+4. Create tag: `git tag -a vX.Y.Z -m "Version X.Y.Z"`
+5. Push: `git push && git push --tags`
+6. Create a new release on GitHub
+7. Build and push the gem: `bundle exec rake release`
+
+## Questions or Need Help?
+
+Feel free to reach out via the GitHub Discussions on this project or by email.
+
+Again, thank you for your interest in contributing to Geminize!

data/LICENSE.txt

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