Relationship filtering - schema inconsistencies

[Lezek123]

Filtering by related entity id

As pointed out by @jodator, there is an inconsitency between the output schema and what is actually supported when it comes to relationship filtering.

For example, previously queries like:

  workers(where: {group_eq:"contentDirectoryWorkingGroup"}) {
    # ...
  }

Were supported (contentDirectoryWorkingGroup is ID of the related WorkingGroup entity in this case).

Currently they have to be rewritten into:

  workers(where: {group: { id_eq: "contentDirectoryWorkingGroup" } }) {
    # ...
  }

But the output schema still contains group_eq and group_in parameters.
Providing any of those currently causes an error:

"column worker.undefined does not exist",

Filtering depth

Another issue is that the output schema doesn't reflect the relationship filtering depth limit, so queries like:

workers(where: { membership: { metadata: { name_eq: "Alice" } } }) {
  # ...
}

Seem to be fine accoring to the schema, but result in an error when executed:

"message": "column membership.undefined does not exist",

[jodator]

I've found a similar case on *Connection type queries where both forms fail. When used:

query {
  workersConnection(where: { group: { id_eq: "forumWorkingGroup" } }) {
    totalCount
  }
}

it returns an error:

"message": "column workinggroupopening.undefined does not exist",

[ondratra]

Basic filtering is done. Recursive filtering as illustrated in #453 (comment) is not yet implemented.