round oar
👋 Hey all,
A function call that was working on v0.15.3 is now throwing...
Error: returned error 422 Unprocessable Entity: {"errors":[{"message":"Cannot query field \"testBackend\" on type \"Platform\".","locations":[{"line":1,"column":16}],"extensions":{"code":"GRAPHQL_VALIDATION_FAILED"}}],"data":null}
Not really sure what in the changelog would relate to seeing this now. 🤔
worthy portal
👋 Hey all,
A function call that was working on v0.15.3 is now throwing...
``...
👋 do you have the module code anywhere?
there's a builtin type called Platform - which doesn't have a field testBackend
what's a bit odd to me is that you were able to declare a Platform type in the first place
round oar
Hey, sorry, the code isn't public. I could try scrap something together but I'll explain for now.
It's the same structure as the dagger quickstart. i.e., an empty struct called Platform with a function TestBackend.
worthy portal
Hey, sorry, the code isn't public. I could try scrap something together but I'll...
yeah the problem is that the Platform type already exists in the api backend - i'd recommend renaming it for now
there is a long term tracking issue for this https://github.com/dagger/dagger/issues/6328
the fact it used to work, is a bit of a stroke of luck - we made changes to improve the validation of our graphql queries, which can catch a lot of subtle issues, so it's sadly not just as simple as disabling it