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: do not send targeting key as separate trait in flagsmith #120

Merged

Conversation

vpetrusevici
Copy link
Contributor

This PR

  • Removes targeting key (identity) from traits list to avoid unnecessary duplication

Vladimir Petrusevici added 2 commits December 21, 2023 16:22
Signed-off-by: Vladimir Petrusevici <V.Petrusevici@maib.md>
Signed-off-by: Vladimir Petrusevici <V.Petrusevici@maib.md>
@vpetrusevici vpetrusevici force-pushed the do-not-send-targeting-key-as-trait branch from ddd69da to 5a6bee7 Compare December 21, 2023 14:23
Copy link
Member

@askpt askpt left a comment

Choose a reason for hiding this comment

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

LGTM! This has a lot of casts but the EvaluationContext doesn't expose a method to remove a key.

@toddbaert toddbaert merged commit 0725f8f into open-feature:main Dec 21, 2023
9 checks passed
luizbon pushed a commit to prospa-group-oss/dotnet-sdk-contrib that referenced this pull request Dec 21, 2023
…eature#120)

Signed-off-by: Vladimir Petrusevici <V.Petrusevici@maib.md>
Signed-off-by: Luiz Bon <luiz.bon@prospa.com>
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.

4 participants