feat: In-memory provider for e2e testing and minimal usage by liran2000 · Pull Request #546

feat: In-memory provider for e2e testing and minimal usage by liran2000 · Pull Request #546 · open-feature/java-sdk

Signed-off-by: liran2000 <liran2000@gmail.com>

changed the title ~~In-memory provider for e2e testing and minimal SDK usage~~ feat: In-memory provider for e2e testing and minimal SDK usage

Aug 7, 2023

Signed-off-by: liran2000 <liran2000@gmail.com>

Signed-off-by: liran2000 <liran2000@gmail.com>

- move to non-test package
- add ContextEvaluator
- update Flags structure
- implement events provider
- enrich tests
- refactor

Signed-off-by: liran2000 <liran2000@gmail.com>

Signed-off-by: liran2000 <liran2000@gmail.com>

Signed-off-by: liran2000 <liran2000@gmail.com>

Signed-off-by: liran2000 <liran2000@gmail.com>

Signed-off-by: liran2000 <liran2000@gmail.com>

Signed-off-by: liran2000 <liran2000@gmail.com>

Signed-off-by: liran2000 <liran2000@gmail.com>

toddbaert changed the title ~~feat: In-memory provider for e2e testing and minimal SDK usage~~ feat: In-memory provider for e2e testing and minimal usage

Aug 14, 2023

verify emit event called on the spied provider as it verifies the config changed event was emitted, which is the in-memory provider implementation. The event itself is a functionality of the events framework, thus not needed to be tested here,

Signed-off-by: liran2000 <liran2000@gmail.com>

…o feat/523-in-memory-provider