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

Change EventMetadata type #234

Closed
askpt opened this issue Feb 12, 2024 · 0 comments · Fixed by #241
Closed

Change EventMetadata type #234

askpt opened this issue Feb 12, 2024 · 0 comments · Fixed by #241
Assignees
Labels
breaking-change Changes in exposed interfaces or behaviour good first issue Good for newcomers help wanted Extra attention is needed

Comments

@askpt
Copy link
Member

askpt commented Feb 12, 2024

FlagMetadata and EventMetadata are shaped the same in the SDK:

I think for consistency, that means we should use the same type for these, which I guess would mean it should be a Dictionary<string, object>() unless there's some way we can bring them in line with your new implementation in a non-breaking way... maybe with extension methods?

Originally posted by @toddbaert in #223 (comment)

@askpt askpt added good first issue Good for newcomers breaking-change Changes in exposed interfaces or behaviour labels Feb 12, 2024
@toddbaert toddbaert added the help wanted Extra attention is needed label Feb 20, 2024
benjiro added a commit that referenced this issue Feb 21, 2024
The spec describes two types(flag metadata, and event metadata) that are functionally the same. This PR
makes a breaking change to bring both of the types to use a generic ImmutableMetadata type.

- Rename BaseMetadata to Immutable, make sealed class and implement a empty constructor

Fixes: #234

Signed-off-by: Benjamin Evenson <[email protected]>
@askpt askpt added this to the 2.0 (breaking) milestone Feb 21, 2024
benjiro added a commit that referenced this issue Feb 24, 2024
The spec describes two types(flag metadata, and event metadata) that are functionally the same. This PR
makes a breaking change to bring both of the types to use a generic ImmutableMetadata type.

- Rename BaseMetadata to Immutable, make sealed class and implement a empty constructor

Fixes: #234

Signed-off-by: Benjamin Evenson <[email protected]>
@benjiro benjiro self-assigned this Feb 25, 2024
toddbaert pushed a commit that referenced this issue Apr 22, 2024
The spec describes two types(flag metadata, and event metadata) that are functionally the same. This PR
makes a breaking change to bring both of the types to use a generic ImmutableMetadata type.

- Rename BaseMetadata to Immutable, make sealed class and implement a empty constructor

Fixes: #234

Signed-off-by: Benjamin Evenson <[email protected]>
toddbaert pushed a commit that referenced this issue Apr 22, 2024
The spec describes two types(flag metadata, and event metadata) that are functionally the same. This PR
makes a breaking change to bring both of the types to use a generic ImmutableMetadata type.

- Rename BaseMetadata to Immutable, make sealed class and implement a empty constructor

Fixes: #234

Signed-off-by: Benjamin Evenson <[email protected]>
arttonoyan pushed a commit to arttonoyan/dotnet-sdk that referenced this issue Nov 17, 2024
…re#241)

## This PR

**BREAKING CHANGE**, merge with 2.0

The spec describes two types(flag metadata, and event metadata) that are
functionally the same. This PR makes a breaking change to bring both of
the types to use a generic ImmutableMetadata type.

- Rename BaseMetadata to ImmutableMetadata, make sealed class and
implement a empty constructor

### Related Issues

Fixes: open-feature#234

---------

Signed-off-by: Benjamin Evenson <[email protected]>
Signed-off-by: Todd Baert <[email protected]>
Co-authored-by: Todd Baert <[email protected]>
Signed-off-by: Artyom Tonoyan <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change Changes in exposed interfaces or behaviour good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants