Trond Sørås

Yeah that makes sense when I see it from the neo4j db side, I agree, but I also agree the behaviour is confusing. The problem I have with your suggested...

For more context, this query also fails with the same error: ```graphql query queryScreenings { screenings( where: { movieConnection: { node: { _on: { NorwegianScreenableMeta: { id: "52a26830-86f8-47b5-bcb5-4ebbf1df2a01" } }...

Simplified schema definition to reproduce the issue: ```graphql type Screening { id: ID! @id interface: MyInterface! @relationship(type: "INTERFACE_CONNECTION", direction: OUT) } interface MyInterface { id: ID! @id } type MyImplementation...

Not blocking, we found a way around it for now 👍

Oddly enough, this error _goes away_ if we change the schema to use an interface instead of a regular type for the `Other` type ```graphql type SomeNode { id: ID!...

We worked around this by adding an interface with only one implementation to fix this for now, and we're looking at options to remove the interfaces from this particular place,...

The eventhandler for the polygoncomplete event will receive a Google Map Polygon object hidden within its arguments. You can get the coordinates like so: ``` $scope.drawingManagerEvents = { polygoncomplete: function(drawingManager,...

I think I just added (.*); at the end of the hex regex and it seemed like it was fixed.