Skip to content

Evaluate without impressions: add impressionsDisabled option to feature evaluation - #452

Merged
ZamoraEmmanuel merged 14 commits into
developmentfrom
evaluate-without-impressions
Dec 16, 2025
Merged

Evaluate without impressions: add impressionsDisabled option to feature evaluation#452
ZamoraEmmanuel merged 14 commits into
developmentfrom
evaluate-without-impressions

Conversation

@EmilianoSanchez

Copy link
Copy Markdown
Contributor

JavaScript commons library

What did you accomplish?

How do we test the changes introduced in this PR?

Extra Notes

@EmilianoSanchez
EmilianoSanchez requested a review from a team as a code ownerNovember 3, 2025 18:17
@EmilianoSanchezEmilianoSanchez changed the title Feat: add impressionsDisabled option to feature evaluation [WIP]Evaluate without impressions: add impressionsDisabled option to feature evaluation [WIP]Nov 3, 2025
@ZamoraEmmanuelZamoraEmmanuel changed the title Evaluate without impressions: add impressionsDisabled option to feature evaluation [WIP]Evaluate without impressions: add impressionsDisabled option to feature evaluationNov 19, 2025
@ZamoraEmmanuel
ZamoraEmmanuel changed the base branch from development to ss-presetDecember 12, 2025 03:44
@ZamoraEmmanuel
ZamoraEmmanuel changed the base branch from ss-preset to developmentDecember 12, 2025 03:45
@ZamoraEmmanuel
ZamoraEmmanuel changed the base branch from development to ss-presetDecember 12, 2025 03:46
return properties && Object.keys(properties).length > 0 ? { properties } : undefined;
let options = properties && Object.keys(properties).length > 0 ? { properties } : undefined;

const impressionsDisabled = maybeOptions.impressionsDisabled;

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

We would need to refactor the validateEvaluationOptions so that the impressionsDisabled option is only validated and used for the Evaluator, and for other SDKs it should be sanitized to false (or any other falsy value) to ignore the feature.

Eventually, if the feature is included in SDKs, the change can be rolled back.

Comment threadtypes/splitio.d.ts Outdated
*
* @defaultValue `false`
*/
impressionsDisabled?: boolean;

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

We should delete this TypeScript definition, if the feature is not supported yet for SDKs.

Comment threadCHANGES.txt Outdated
Base automatically changed from ss-preset to developmentDecember 15, 2025 15:39
Comment threadCHANGES.txt Outdated
@ZamoraEmmanuel
ZamoraEmmanuel merged commit eaf04b8 into developmentDec 16, 2025
2 checks passed
@ZamoraEmmanuel
ZamoraEmmanuel deleted the evaluate-without-impressions branch December 16, 2025 20:53
Sign up for freeto 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

@EmilianoSanchez@ZamoraEmmanuel