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

[FFM-5510]: Fixing the condition in evaluator to consider empty slice + expose Evaluate function #104

Merged
merged 2 commits into from
Nov 25, 2022

Conversation

akiraqb
Copy link
Contributor

@akiraqb akiraqb commented Nov 24, 2022

[FFM-5510]: Fixing the condition in evaluator to consider empty slice + Exposing Evaluate function
# What: 
Small fix to consider empty slice in the condition for clause evaluation
# Why:
Previously segment.rules would either be nil pointer or pointer to slice with at least one element.
Due to changes made for FFM-4150 we require extra check. 
# Testing:
Locally

@akiraqb akiraqb changed the title Fixing the condition in evaluator to consider empty slice + expose Evaluate function [FFM-5510]: Fixing the condition in evaluator to consider empty slice + expose Evaluate function Nov 24, 2022
Copy link
Contributor

@davejohnston davejohnston left a comment

Choose a reason for hiding this comment

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

Ship it!

@akiraqb akiraqb merged commit 875e3de into main Nov 25, 2022
davejohnston pushed a commit to davejohnston/ff-golang-server-sdk that referenced this pull request Sep 26, 2023
… + expose Evaluate function (harness#104)

[FFM-5510]: Fixing the condition in evaluator to consider empty slice + Exposing Evaluate function
# What: 
Small fix to consider empty slice in the condition for clause evaluation
# Why:
Previously segment.rules would either be nil pointer or pointer to slice with at least one element.
Due to changes made for FFM-4150 we require extra check. 
# Testing:
Locally
@erdirowlands erdirowlands deleted the FFM-5510 branch November 3, 2023 17:46
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.

None yet

2 participants