Skip to content

Add "static-context" paradigm OFEP#41

Merged
toddbaert merged 6 commits intomainfrom
ofep/single-context-paradigm
May 18, 2023
Merged

Add "static-context" paradigm OFEP#41
toddbaert merged 6 commits intomainfrom
ofep/single-context-paradigm

Conversation

@toddbaert
Copy link
Copy Markdown
Member

@toddbaert toddbaert commented Dec 23, 2022

As discussed in the 22nd community meeting, this draft outlines a new "static-context" paradigm to better support client/web use-cases.

The key changes in this paradigm are:

  • the lack a context parameter on evaluation methods
  • the lack of a context setter on the client class
  • a optional method in providers that is called when the global context is changed, which the provider can use to "reconcile" it's context

For more information, please see the OFEP.

I believe this, combined with disposal and events, represent the basis for proper client support in the spec.

toddbaert and others added 2 commits December 23, 2022 15:26
Co-authored-by: Michael Beemer <[email protected]>
Signed-off-by: Todd Baert <[email protected]>
@toddbaert toddbaert requested a review from beeme1mr February 15, 2023 18:39
@toddbaert toddbaert changed the title Add "single-context" paradigm OFEP Add "static-context" paradigm OFEP Feb 15, 2023
Copy link
Copy Markdown
Member

@moredip moredip left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the proposal overall. I particularly like that we're quite aggressively removing API surface area wrt. different ways of setting evaluation context.

I suspect at some point down the line we will look at how to support multiple independent evaluation contexts (e.g. for different teams, or for different screens in the UI). I don't think that this proposal is going to make it harder to add that in in the future.

Copy link
Copy Markdown
Member

@beeme1mr beeme1mr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excited to bring OpenFeature to the client.

@github-actions
Copy link
Copy Markdown

This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in next 60 days.

@github-actions github-actions bot added the Stale label May 18, 2023
@toddbaert toddbaert removed the Stale label May 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants