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

fix: various clarifications #193

Merged
merged 3 commits into from
Jun 2, 2023
Merged

fix: various clarifications #193

merged 3 commits into from
Jun 2, 2023

Conversation

toddbaert
Copy link
Member

@toddbaert toddbaert commented May 31, 2023

cc @open-feature/technical-steering-committee @lopitz @lukas-reining @kinyoklion @Kavindu-Dodan

Definitely let me know anyone thinks something is missing or could be improved here.

* loosen shutdown requirements to support things like go ctx
* clarify how to handle init/shutdown of providers bound to multiple names
* clarify init function should terminate before provider used

Signed-off-by: Todd Baert <todd.baert@dynatrace.com>
specification.json Outdated Show resolved Hide resolved
Signed-off-by: Todd Baert <todd.baert@dynatrace.com>
specification.json Outdated Show resolved Hide resolved
Copy link
Contributor

@Kavindu-Dodan Kavindu-Dodan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving - Open discussions can be finalized on agreements and personaly I don't see them to conflict a lot

specification.json Outdated Show resolved Hide resolved
Signed-off-by: Todd Baert <todd.baert@dynatrace.com>
Copy link
Member

@lukas-reining lukas-reining left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me now and the changes are really good to me!

@toddbaert toddbaert merged commit 77e0b9c into main Jun 2, 2023
@toddbaert toddbaert deleted the fix/various-clarifications branch June 2, 2023 19:38
@s-sen
Copy link

s-sen commented Jun 13, 2023

The spec shows that the initialization accepts a global context as a parameter. However the java sdk provider interface has the initialization API without any parameters. Is there any discussion regarding that?

@toddbaert
Copy link
Member Author

toddbaert commented Jun 13, 2023

The spec shows that the initialization accepts a global context as a parameter. However the java sdk provider interface has the initialization API without any parameters. Is there any discussion regarding that?

I think this is an oversight. I will open an issue in the Java SDK (we haven't released yet, so no issue). Great find.

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.

9 participants