#316: Add helper func to get activity titles from ids in Opp-List

[DarrellRoberts]

Description

• Adds helper func to get activity titles from ids in the options array. This was neccessary to display activities in the opportunity cards

• Adds Activity filter

Related Issues

Closes #316

Changes

• Bullet list of meaningful changes (optional)

Screenshots / Demos

Checklist

• WITHIN THE SCOPE OF AN ISSUE; No unnecessary files included
• Tests added/updated
• Documentation updated
• CI passes

[DarrellRoberts]

ACTIVITY is not part of QueryParamsKeys hence why I went for EntityTableName. But I can update the sdk if needed

[nadavosa]

Review

Issue 1 — Activity filters won't restore from URL

In src/components/Dashboard/Opportunities/Filters/helpers.ts, the deserialization loop:

```ts
queryActivities.forEach((l) => {
if (newFilter.activity[l] !== undefined) newFilter.activity[l] = true;
});
```

defaultOpportunityCardsFilter initializes activity as {}, so every key is undefined — the condition is always false and activity filters are never restored from the URL when navigating back.

Fix:
```ts
queryActivities.forEach((l) => {
newFilter.activity[l] = true;
});
```

Issue 2 — Type consistency in getActivityTitles

In src/components/Dashboard/Opportunities/helpers.ts:
```ts
const activityMap = new Map(activityList.map((item) => [item.id, item.title])); // key: number
return activities.map((act) => activityMap.get(Number(act.id))) // lookup: Number(string)?
```

act.idanditem.idare the same type at runtime.? Ifact.idis a string, the map lookup will always miss (different types as Map keys). Safest fix is to key everything withString(id)` consistentl

[DarrellRoberts]

thanks for the review @nadavosa ! I've committed those changes now

[DarrellRoberts]

FYI I've noticed we're not actually importing/using the deserializeOpportunityFilters function (the function that will automatically add filters when the URL is pasted/refreshed). I did start to implement it in /Opportunities.tsx but realise I should probably do it in a seperate issue/PR

[need4deed]

FYI I've noticed we're not actually importing/using the deserializeOpportunityFilters function (the function that will automatically add filters when the URL is pasted/refreshed). I did start to implement it in /Opportunities.tsx but realise I should probably do it in a seperate issue/PR

Yes this is important, we alwasy need to refilter because oft that - can you open an issue?

[DarrellRoberts]

sure thing