Skip to content
This repository was archived by the owner on Dec 6, 2025. It is now read-only.
This repository was archived by the owner on Dec 6, 2025. It is now read-only.

Proper model for PropertyValue values #860

@FoseFx

Description

@FoseFx

Describe the chore

Currently, we cast it into an interface{}, which throws away vital information.

Is this a string because it's an option, or a text, or a multi-select option?

We could embrace TypedValue and give it proper serialization to esdb

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions