Entity description query for once user selects Entity about chainverse-frontend

[clemp]

MATCH (d:Entity {name:$name})
OPTIONAL MATCH (d)-[:HAS_PROPOSAL]->(:Proposal)<-[:VOTED]-(sm:Wallet)
WITH d, COUNT(DISTINCT sm) as snapshot_members
OPTIONAL MATCH (d)<-[:IS_MEMBER]-(dm:Member)
WITH d, snapshot_members, COUNT(DISTINCT dm) as DAOHaus_members
RETURN snapshot_members, DAOHaus_members, d.forum as forum, d.discord as discord, d.documentation as documentation, d.twitter as twitter, d.opensea as OpenSea, d.blog as blog

This query assumes some properties that are not currently present in the type definitions for Entities. Here's the properties of Entity (as is currently in develop)

chainverse-frontend/src/services/Apollo/typedefs.ts

Lines 12 to 27 in cf064b8

	type Entity {
	"""
	TODO: Should this be restricted
	"""
	uuid: ID @id(autogenerate: true)
	name: String @unique #under assumption name for entities are unique
	id: String @unique
	minScore: Float
	network: Float
	onlyMembers: String
	symbol: String
	address: String @unique
	avatar: String
	about: String
	proposals: [Proposal] @relationship(type: "HAS_PROPOSAL", direction: OUT)
	}

I know @musubipapi is expanding these by creating unions of different Entity types (is there a Pull Request open for this change?); for example, Entity:Snapshot properties will be different than Entity:DAOhaus properties.

@Azharo For the properties you list here above: opensea, documentation, etc - how do you envision these aligning to specific Entity types as laid out in the GraphQL API type definitions?

[Azharo]

These properties will eventually just get taken out as separate nodes attached to each :Entity which hasn't been done yet. That'll remove any problems with the union since right now the Union is only really going to have name property.
This way we can connect different Entities as the same entity if they reference the same descriptor such as they have the same twitter handle or medium.
I'll add to issue that we need to expand these out as nodes and not keep as properties

Change current code snippet above to the following so it works even with our GraphQL types so at least we have it working in the UX while we make the right changes on the backend:

MATCH (d:Entity {name:$name})
OPTIONAL MATCH (d)-[:HAS_PROPOSAL]->(:Proposal)<-[:VOTED]-(sm:Wallet)
WITH d, COUNT(DISTINCT sm) as snapshot_members
OPTIONAL MATCH (d)<-[:IS_MEMBER]-(dm:Member)
WITH d, snapshot_members, COUNT(DISTINCT dm) as DAOHaus_members
OPTIONAL MATCH (dao:DaoHaus:Dao {name:$name})
RETURN snapshot_members, DAOHaus_members, dao.forum as forum, dao.discord as discord, dao.documentation as documentation, dao.twitter as twitter, dao.opensea as OpenSea, dao.blog as blog