Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[BUG] client handlers do not run immediately if associated provider is in matching state. #700

Closed
toddbaert opened this issue Nov 30, 2023 · 0 comments · Fixed by #701
Closed

[BUG] client handlers do not run immediately if associated provider is in matching state. #700

toddbaert opened this issue Nov 30, 2023 · 0 comments · Fixed by #701
Assignees
@toddbaert
Labels
bug Something isn't working

Comments

@toddbaert
Copy link
Member

Observed behavior

client handlers do not run immediately if associated provider is in matching state.

Expected Behavior

client handlers should run immediately if associated provider is in matching state: https://openfeature.dev/specification/sections/events#requirement-533

Steps to reproduce

No response
@toddbaert toddbaert added the bug Something isn't working label Nov 30, 2023
@toddbaert toddbaert self-assigned this Nov 30, 2023
This was referenced Nov 30, 2023
Merged
Merged
github-merge-queue bot pushed a commit that referenced this issue Dec 1, 2023
@toddbaert
fix: handlers should run immediately (#701)
dba858b 
* web-sdk handlers should run immediately if provider in matching state
* added tests for both server and client

Fixes: #700

Signed-off-by: Todd Baert <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@toddbaert toddbaert

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: handlers should run immediately open-feature/js-sdk
1 participant
@toddbaert