Skip to content

fix: [GO Feature Flag server] handle PROVIDER_NOT_READY from the spec#505

Merged
thomaspoignant merged 2 commits intomainfrom
return-err-if-provider-not-ready
Jul 31, 2023
Merged

fix: [GO Feature Flag server] handle PROVIDER_NOT_READY from the spec#505
thomaspoignant merged 2 commits intomainfrom
return-err-if-provider-not-ready

Conversation

@thomaspoignant
Copy link
Member

@thomaspoignant thomaspoignant commented Jul 31, 2023

This PR

  • Return an error if we try to evaluate before the provider is ready.
  • Rewrite the tests to use the SDK and not test only the provider.

Signed-off-by: Thomas Poignant <thomas.poignant@gofeatureflag.org>
@thomaspoignant thomaspoignant requested a review from a team as a code owner July 31, 2023 07:22
@thomaspoignant thomaspoignant changed the title fix: [GO Feature Flag server'handle PROVIDER_NOT_READY from the spec fix: [GO Feature Flag server] handle PROVIDER_NOT_READY from the spec Jul 31, 2023
Signed-off-by: Thomas Poignant <thomas.poignant@gofeatureflag.org>
Copy link
Member

@toddbaert toddbaert left a comment

Choose a reason for hiding this comment

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

I've found this testing style to be better for providers, though maybe some people prefer "unit"-level tests.

Looks good!

@thomaspoignant
Copy link
Member Author

I've found this testing style to be better for providers, though maybe some people prefer "unit"-level tests.

I'll prefer it too, that's what I've done for other providers but this one the 1st one and I haven't done it properly the 1st time :D

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