Closed olivermt closed 6 years ago
And yes I have fixed the spelling error langitude -> latitude, still same error :)
Also, to save you the hassle of reading the fine print, Arg 1: %{data: %{coordinates: %{latitude: 29.769673597523774, longitude: -115.62357985340464}}, data_type: "centre", description: "Playa Escolete section", id: 1078, inserted_at: ~N[2018-03-19 10:26:40.169642], name: "Playa Escolete section", outcrop_id: 58008, updated_at: ~N[2018-03-19 10:26:40.169668]}
Arg 2: The blueprint in its entirety, cant see anything useful there.. a whole lot of references to various lines in the file, seems to be one per object and enum
And lastly, it turns out the graphiql interface has the non-truncated version as well.
So here is that too:
Lastly, I'm uninstalling elixir and getting a job flipping burgers at mcdonalds...
I was calling resolve_type with just one arg, it more or less said so in clear text ffs 😿
@olivermt Take it easy on yourself! :-) Best of luck; we're here for you if you run into another issue.
Just adding a clarifying comment here (as I fell in the same hole):
resolve_type fn
%Person{}, _ -> :person
%Business{}, _ -> :business
end
is different from
resolve_type fn
%Person{} -> :person
%Business{} -> :business
end
For me, it has been non-standard to use anonymous functions with multiple bodies. But I learned something new!
If submitting a bug, please provide the following:
Environment
Expected behavior
fields with data for query:
Actual behavior
I truncated the output, the rest are some security tokens + the entire blueprint.
I am transforming the binary map keys to atom keys, because I intially thought that was why it went boom before I read error more closely.
Relevant Schema/Middleware Code
Relevant schema:
Relevant middleware / resolver:
Service module that provides the data:
The batch_many etc comes from a macro, I just put it into the same module for documentation purposes
And at last, the data returned to the batcher for georef on outcrop, that the Map.get acts on (this is valid data):