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.

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

feat(eventing): add support for state change reactions #20

Merged
merged 6 commits into from
Dec 14, 2024

Conversation

ubabar123
Copy link

This PR

  • Adds eventing feature to react to state changes in the provider or flag system.

Notes

This feature includes event hooks for providers and flag changes.

Follow-up Tasks

  • Add tests for edge cases in the eventing system.

How to test

  • Run the project.
  • Simulate provider or flag changes to confirm the eventing feature triggers correctly.

@ABC2015
Copy link

ABC2015 commented Dec 14, 2024

@ubabar123 Looks good to me - it looks like there a a couple of conflicts that need resolution first. Conflicting files
open-feature-dart-server-sdk/.dart_tool/package_config.json
open-feature-dart-server-sdk/lib/open_feature_api.dart

@ABC2015
Copy link

ABC2015 commented Dec 14, 2024

@ubabar123 ok looks good to me. Merging into the QA branch now.

@ABC2015 ABC2015 merged commit 0ac17bd into open-feature:qa Dec 14, 2024
15 checks passed
ABC2015 pushed a commit that referenced this pull request Dec 17, 2024
## This PR
- Adds eventing feature to react to state changes in the provider or
flag system.



### Notes
This feature includes event hooks for providers and flag changes.

### Follow-up Tasks
- Add tests for edge cases in the eventing system.

### How to test
- Run the project.
- Simulate provider or flag changes to confirm the eventing feature
triggers correctly.

---------

Signed-off-by: Usman <[email protected]>
Signed-off-by: ubabar123 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants