ysads / nukr Goto Github PK

This would make connections more qualified, since they can have their own attributes, and maybe be qualitatively described. This allows, for example, a user to have connections which describe friends, family, people they know and etc.

This would also include a new namespace nukr.entities.connection which would hold a Connection record.

Also, a new route would be necessary: GET /profiles/:uuid/connections, which would respond with a collection of connection objects a given profile has, grouped by their type attribute.

This is intended to make connections more versatile, by allowing them to be directional and assymetric. That is, if A is connected to B, not necessarely B is connected to A - sort of like how Twitter works.

I think of handling the storage records much like Datomic do: user must specify under which entity a given record will be inserted.

This makes possible for the component to handle different entities under the same storage adapter - for example, connections and profiles -, which makes it behave like a normal database.

Two approaches may be considered when implementing this:

• Insert the records under a second-level-deep key, in such a way that the first-level key is the entity name.
• Insert into a custom entity key into the record map, containing the entity name. This doesn't allow a constant-time finding if we want to restrict our search to a given entity, but rather makes it trivial finding to which entity a record belongs.