-
Notifications
You must be signed in to change notification settings - Fork 35
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: introduce appendix section #199
feat: introduce appendix section #199
Conversation
Signed-off-by: Kavindu Dodanduwa <kavindudodanduwa@gmail.com>
d8946df
to
aabc3aa
Compare
Signed-off-by: Kavindu Dodanduwa <kavindudodanduwa@gmail.com>
Co-authored-by: Todd Baert <todd.baert@dynatrace.com> Signed-off-by: Kavindu Dodanduwa <Kavindu-Dodan@users.noreply.github.com>
Signed-off-by: Kavindu Dodanduwa <kavindudodanduwa@gmail.com>
Signed-off-by: Kavindu Dodanduwa <kavindudodanduwa@gmail.com>
Relative to most spec changes, this one seems low risk and high reward. I personally would love to remove the dependency cycle in our SDK repos that results from including the flagd provider. The OFEP was also well-received, so I'm going to merge this EOD unless I hear objections. |
Just to check, this would effectively deprecate the caching tests scenarios declared in the e2e test-harness when using the in-memory provider, right? |
Co-authored-by: Federico Bond <federicobond@gmail.com> Signed-off-by: Todd Baert <todd.baert@dynatrace.com>
Co-authored-by: Federico Bond <federicobond@gmail.com> Signed-off-by: Todd Baert <todd.baert@dynatrace.com>
Yes, good call. I think the caching tests are no longer relevant, and beyond the scope of what SDKs should be testing. In fact, we may want to move the gherkin suite(s) into their own appendix in the spec and de-emphasize the test-harness repo, which is tightly associated with flagd. |
This PR
Adds an appendix section [1]
Appendix is expected to contain extra information for both OpenFeature maintainers and users
[1] - open-feature/ofep#71 (comment)