Skip to content

PM-4168 fix open to work status#94

Merged
vas3a merged 1 commit intodevelopfrom
PM-4168_open-to-work
Mar 5, 2026
Merged

PM-4168 fix open to work status#94
vas3a merged 1 commit intodevelopfrom
PM-4168_open-to-work

Conversation

@vas3a
Copy link
Collaborator

@vas3a vas3a commented Mar 5, 2026

No description provided.

@vas3a vas3a merged commit 9b543c8 into develop Mar 5, 2026
3 of 4 checks passed
@vas3a vas3a deleted the PM-4168_open-to-work branch March 5, 2026 10:12
if (item.traitId === 'personalization' && item.traits.data.length > 0 && !data.engagementAvailability) {
const openToWorkTrait = item.traits.data.find(r => Object.keys(r).includes('openToWork')) || {};
const openToWorkData = openToWorkTrait.openToWork || {};
const openToWorkData = openToWorkTrait.openToWork;
Copy link

Choose a reason for hiding this comment

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

[❗❗ correctness]
The change from openToWorkTrait.openToWork || {} to openToWorkTrait.openToWork removes the default empty object fallback. This could lead to a TypeError if openToWorkTrait.openToWork is undefined and is accessed later. Consider ensuring openToWorkTrait.openToWork is defined before accessing its properties.

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.

1 participant