Feature/session colors

[interim17]

Time Estimate or Size

medium

related website branchs:
fix/update-ssi -> a patch to bring website into alignment with this changeset feature/color-session -> the end goal for the feature in development

Advances #510 and #511

Problem

On the front end we need to be storing and applying sets of color changes (browser sessions, or re-applying default). Current code assumes one-color-change-at-a-time.

Solution

UIDisplayData is a good existing data structure that conveys a snapshot of agent tree and its colors.

In SelectionStateInfo colorChanges have been replaced by appliedColors of type UIDisplayData

This is more consistent with the other parts of the selection object which serves as a snapshot of the selection state, rather than as a pass-through for a series of changes.

Keeping this change set small. Possible further changes would keep the SelectionInterface entries object in sync with "rendered state"... Might be useful for writing changes out to new files, not needed right now for MVP.

Type of change

• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

[github-actions[bot]]

jest coverage report 🧪

Total coverage

Status	Category	Percentage	Covered / Total
🔴	Statements	40.95%	2043/4989
🔴	Branches	43.21%	838/1939
🔴	Functions	36.92%	418/1132
🔴	Lines	41.17%	1956/4751

Status of coverage: 🟢 - ok, 🟡 - slightly more than threshold, 🔴 - under the threshold

Show files with reduced coverage 🔻

### Reduced coverage | Status | Filename | Statements | Branches | Functions | Lines | | :----: | :-------------- | :--------- | :------- | :-------- | :------ | | 🔴 | index.ts | 7.69% | 7.25% | 5.64% | 7.65% | | 🔴 | src/viewport | 14.09% | 10.52% | 13.95% | 13.65% | | 🔴 | index.tsx | 14.09% | 10.52% | 13.95% | 13.65% | | 🔴 | src/visGeometry | 21.76% | 22.79% | 27.5% | 21.63% | > Status of coverage: 🟢 - ok, 🟡 - slightly more than threshold, 🔴 - under the threshold

[interim17]

looks good, I would pull out the AgentData fix into it's own PR and make sure the exports are consistent with how we're exporting all the other types from the system

For context for other reviewers, this is done, the fix has been merged into both main and this branch.