Skip to content

Separate technical types from Data Structure #158

@dtrzesniak

Description

@dtrzesniak

Currently, the whole model is there and it's becoming too complex.
We should refactor the file and separate the concerns.
Especially the technical types, like KeyedRecord and so on

I would like to have:

  • business content separated from technical
  • generic separated from specific (reporting node is generic, while liability type is specific --> where is the line?)
  • dimensions/parameters/args/poco/identities types --> how do we want to group these? I would prefer to have those types that are not stored separated is a group separated from things like args and identities. data/poco types maybe too --> let's discuss.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status

    🆕 New

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions