You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a data structure that corresponds to GeoJSON Multipolygon, which is:
[[[[Float!]!]!]!]!
However I get the error: decorated type deeper than introspection query
I presume it has to do with the nested array. Is there a way to introspect this kind of data structure, or to not lose introspection on the whole graph?
Here is a type with a field (multipolygon) that produces the issue
type GeoJSON {
type: String!
boundingbox: [Float!]
point: [Float!]
multipoint: [[Float!]!]
linestring: [[Float!]!]
multilinestring: [[[Float!]!]!]
polygon: [[[Float!]!]!]
multipolygon: [[[[Float!]!]!]!]
}
The problem starts on field multipolygon. If I erase this, everything works the way it should.
The text was updated successfully, but these errors were encountered:
gschier
changed the title
Error: decorated type deeper than introspection query
[Bug] Decorated type deeper than introspection query
Aug 1, 2018
That's an interesting one. It looks like this might be solved by updating our graphql dependency (Insomnia does not deal directly with introspection queries).
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Details
I have a data structure that corresponds to GeoJSON Multipolygon, which is:
[[[[Float!]!]!]!]!
However I get the error: decorated type deeper than introspection query
I presume it has to do with the nested array. Is there a way to introspect this kind of data structure, or to not lose introspection on the whole graph?
Here is a type with a field (multipolygon) that produces the issue
type GeoJSON {
type: String!
boundingbox: [Float!]
point: [Float!]
multipoint: [[Float!]!]
linestring: [[Float!]!]
multilinestring: [[[Float!]!]!]
polygon: [[[Float!]!]!]
multipolygon: [[[[Float!]!]!]!]
}
The problem starts on field multipolygon. If I erase this, everything works the way it should.
The text was updated successfully, but these errors were encountered: