We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As proposed by OFEP: SDK end-to-end test strategy 1, we should create an in-memory provider for Java-sdk
We already have contributions for Python2 & Go 3, and we can use same flag format, constructors & error handling strategy for this implementation.
https://github.com/open-feature/java-sdk/issues/523
https://github.com/open-feature/ofep/pull/71 ↩
https://github.com/open-feature/python-sdk/pull/157 ↩
https://github.com/open-feature/go-sdk/pull/192 ↩
https://github.com/open-feature/java-sdk/tree/main/src/test/java/dev/openfeature/sdk/e2e ↩
The text was updated successfully, but these errors were encountered:
Small related PR here: #543
Sorry, something went wrong.
@Kavindu-Dodan @toddbaert as PR merged, can be resolved ?
@liran2000 yes, this is complete. Thank you for working on this 🙌
No branches or pull requests
As proposed by OFEP: SDK end-to-end test strategy 1, we should create an in-memory provider for Java-sdk
We already have contributions for Python2 & Go 3, and we can use same flag format, constructors & error handling strategy for this implementation.
https://github.com/open-feature/java-sdk/issues/523
for related TODOs.Footnotes
https://github.com/open-feature/ofep/pull/71 ↩
https://github.com/open-feature/python-sdk/pull/157 ↩
https://github.com/open-feature/go-sdk/pull/192 ↩
https://github.com/open-feature/java-sdk/tree/main/src/test/java/dev/openfeature/sdk/e2e ↩
The text was updated successfully, but these errors were encountered: