fixed critical bug in configuration and add specs

[Reion19]

[ ✅ ] Have you followed the guidelines in our Contributing document?
[ ✅ ] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[ ✅ ] Have you added an explanation of what your changes do and why you'd like us to include them?

---

Summary:

• Fixed critical bugs in the configuration that were affecting the correct behavior of the gem.
• Rewrote the specs to match the current configuration logic.

Notes:

• All specs are now passing.
• Changes are mostly backward-compatible with the current version of the gem.

[a1xsh]

Do not add comments inside the params

[Reion19]

Ok, roger that, that comment will be removed

[a1xsh]

Add providers in the top

[Reion19]

I'll move the providers to the top of the file for better organization.

[a1xsh]

Do not add comments like this inside code.

[Reion19]

Understood, I'll remove all comments like this. Thanks!

[a1xsh]

Do not add comments like this inside code.

[Reion19]

Got it, I’ll remove the comment from the code. Thanks!

[a1xsh]

Do not add any To-do in comments!

[a1xsh]

You can open a new ticket/issue

[Reion19]

Understood! I’ll remove the TODO comment and create an issue/ticket. Thanks!

[a1xsh]

Do we need this also?

[Reion19]

Sorry, could you please specify what part you mean? I’m not sure what you're referring to.

[a1xsh]

do we need require require_relative "rubyai/provider"
if we have required all of them directly?

[a1xsh]

But we can use the module Provider.

[Reion19]

Thanks!

I agree.

i will update it

[a1xsh]

Too many variables inside the initialize. Should be <5

[Reion19]

Thanks I’ll refactor the initialize method.

[a1xsh]

As well

 lib/rubyai.rb

    Entry point. Requires all other files.

require "rubyai/version"
require "rubyai/configuration"
require "rubyai/client"
require "rubyai/chat"
require "rubyai/http"
require "rubyai/provider"
require "rubyai/providers/base"
require "rubyai/providers/openai"
require "rubyai/providers/anthropic"
require "rubyai/providers/gemini"

Configuration

All global configuration, e.g. API keys, default provider, timeouts.

• provider.rb is the abstract base class or module for all providers.
• providers/base.rb is optional, but some like a clean separation for all common logic.
• Each provider lives in its own file in providers/.
• The main client can dynamically select a provider based on user config.

# lib/rubyai/providers/base.rb
module RubyAI
  module Providers
    class Base
      def initialize(options = {})
        # set up keys, etc.
      end

      def chat(messages:, **opts)
        raise NotImplementedError
      end

      # Optionally define common helper methods
    end
  end
end

# lib/rubyai/providers/openai.rb
module RubyAI
  module Providers
    class OpenAI < Base
      def chat(messages:, **opts)
        # OpenAI-specific logic
      end
    end
  end
end

client.rb acts as the main user entry point, initializes the provider, delegates requests.

module RubyAI
  class Client
    def initialize(provider: :openai, **opts)
      @provider = build_provider(provider, opts)
    end

    def chat(messages:, **opts)
      @provider.chat(messages: messages, **opts)
    end

    private

    def build_provider(provider, opts)
      case provider.to_sym
      when :openai then Providers::OpenAI.new(opts)
      when :anthropic then Providers::Anthropic.new(opts)
      when :gemini then Providers::Gemini.new(opts)
      # Add more as needed
      else
        raise ArgumentError, "Unknown provider: #{provider}"
      end
    end
  end
end

Configuration

RubyAI.configure do |config|
  config.api_key = ENV["OPENAI_API_KEY"]
  config.default_provider = :openai
  # etc.
end

[Reion19]

I have a few questions:

1. Which logic should be placed inside the chat.rb file?

2. Currently, we can chat with different providers via RubyAI::Client or RubyAI::Chat.
   Do we need to move the chat logic into the providers' logic, or is it better to keep it as it is now?