Max VelDink

feat: adds allFlagMetadata to clients and provider interface

3

## This PR Adds an optional `allFlagMetadata` accessor to clients and the provider interface for retrieving a list of flag keys available in the provider. - Adds requirements for `allFlagMetadata`...

When autocorrecting the Sorbet/ValidSigil cop on files without any magic string comments at the top, it adds the sigil without an extra newline like so: ```ruby # typed: false class...

@mschoenlaub brought up some great points about concurrency in [this PR](https://github.com/open-feature/ruby-sdk/pull/136). I'd like to continue that discussion here, as well as think through some example concurrent apps (maybe using the...

Implement Requirement 1.3.4 (type mismatch check in client)

2

While reviewing #124, I realized that we were doing too much work in our `InMemoryProvider` implementation for verifying type mismatches. In fact, [Requirement 1.3.4](https://openfeature.dev/specification/sections/flag-evaluation#requirement-134) indicates that the client should ultimately...

Update README to match template

2

There is an [OF README template](https://github.com/open-feature/.github/tree/main/templates/READMEs) that we should be using for the Ruby gem.

Re-evaluate `OpenFeature` file naming

3

While working on #72, I encountered a [rule violation around spec naming](https://docs.rubocop.org/rubocop-rspec/cops_rspec.html#rspecspecfilepathformat). I believe this was because the files were named `openfeature` while the constant we're defining is `OpenFeature`. In...

Spec for reference: https://openfeature.dev/specification/sections/evaluation-context#33-context-propagation

There is no spec version here, but we should look to provide guidance and basic logging support for something like the `Rails.logger`.

refactor: changed client metaprogramming to send with real methods

1

## This PR - adds this new feature ### Related Issues Fixes #1234523 ### Notes ### Follow-up Tasks ### How to test