Skip to content

Conversation

@alxckn
Copy link
Contributor

@alxckn alxckn commented Apr 30, 2024

Fixes #123

Upper cases error and reason enum values and adds missing 'PROVIDER_FATAL' error

@alxckn alxckn requested a review from a team as a code owner April 30, 2024 16:37
@beeme1mr beeme1mr changed the title Use strings from spec for error and reason enums fix: Use strings from spec for error and reason enums Apr 30, 2024
@alxckn alxckn changed the title fix: Use strings from spec for error and reason enums feat: Use strings from spec for error and reason enums Apr 30, 2024
@codecov
Copy link

codecov bot commented Apr 30, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.48%. Comparing base (33843f9) to head (3353179).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #131   +/-   ##
=======================================
  Coverage   99.48%   99.48%           
=======================================
  Files          15       15           
  Lines         195      196    +1     
=======================================
+ Hits          194      195    +1     
  Misses          1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@beeme1mr beeme1mr requested a review from maxveldink April 30, 2024 17:47
Copy link
Contributor

@maxveldink maxveldink left a comment

Choose a reason for hiding this comment

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

Thanks for the contribution! First one to the primary SDK I believe 🎉

Technically, this is a breaking change if someone is relying on those backing strings, so we'll want to name this feat!: ... for a breaking change.

@beeme1mr beeme1mr changed the title feat: Use strings from spec for error and reason enums feat!: Use strings from spec for error and reason enums May 1, 2024
@beeme1mr beeme1mr merged commit cb2a4cd into open-feature:main May 1, 2024
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.

Use specification values for error and reason enum

4 participants