feat: STALE state, run handlers for current state immediately, provider name

open-feature / spec

OpenFeature specification

https://openfeature.dev

Apache License 2.0

595 stars 35 forks source link

feat: STALE state, run handlers for current state immediately, provider name #196

Closed toddbaert closed 10 months ago

toddbaert commented 1 year ago

Adds additional clarity regarding provider/client name mapping, as well as intent
Replaces client-name for provider-name in events-details
adds "STALE" state
handlers for ANY state run immediately if provider is in that state

The only functional changes here are small ones related to events, and a new provider state, so particularly interested in @Kavindu-Dodan and @lukas-reining 's opinions on this one.

Relates to https://github.com/open-feature/spec/pull/200, which depends on STALE state.

toddbaert commented 10 months ago

@Kavindu-Dodan @lukas-reining @beeme1mr @Kavindu-Dodan I've updated this PR. Please re-review.

The main change is the addition of the STALE provider state, and changes to 5.3.3: instead of just READY events running immediately, now the spec dictates that handlers of any type should run immediately if they are added when the provider is already in the associated state.